Read published post summaries and public tags using a Ghost Content API key and the exact HTTPS Content API URL. Fixed field selection excludes rich bodies, author payloads and code injection. Requires API v6.0 or newer. This is separate from Ghost Admin API and excludes drafts, members, publishing changes and managed OAuth.
What you can do (3)
What you can do
Available commands: 3 (3 read, 0 write). Enable only the commands your application needs.
| Command | Effect |
|---|---|
List published post summaries — ghostcontent.posts.list |
Read |
Read a published post summary — ghostcontent.posts.get |
Read |
List public tag summaries — ghostcontent.tags.list |
Read |
Connect and use
Open the integration's connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.
Get your provider credentials
Follow these steps for Ghost Content API, then enter the issued values in the connection form below.
- Sign in to your Ghost Admin and open Settings > Integrations. Create a Custom Integration, copy its Content API URL into Ghost Content API URL and its Content API key into Ghost Content API key in this connection form. Copy the full URL ending in /ghost/api/content/; the admin domain may differ from your publication domain. HTTPS custom admin domains and installations under a subdirectory are supported through the existing public-address transport checks. Do not use the Admin API key or strip its signing secret into this field: that is a separate integration. These reads require Ghost API v6.0 or newer. Save, allow the desired reads and call an example with your Tooluse.net API key. Only published post summaries and public tags are requested, with explicit pagination. No drafts, rich bodies, member data, publishing changes or managed OAuth. Regenerate the Content API key in Ghost Admin if needed and update the saved connection.
Where to enter credentials
In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.
| Connection field | Requirement |
|---|---|
| Ghost Content API URL | Required |
| Ghost Content API key | Required |
Open API keys and create a Tooluse.net key for the enabled commands.
Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.
Configure Claude Code, Codex or Cursor once
Permissions and results
If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.
Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.
Call from your client
Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.
Configure Claude Code, Codex or Cursor once
Discover your enabled tools
List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.
curl 'https://api.tooluse.net/v1/tools' \
-H "Authorization: Bearer $TOOLUSE_API_KEY"
Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.
HTTP call
curl 'https://api.tooluse.net/v1/tool-calls' \
-H "Authorization: Bearer $TOOLUSE_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: replace-with-a-new-call-id' \
--data '{
"type": "tool_use",
"id": "toolu_example",
"name": "svc_FROM_YOUR_TOOL_LIST",
"input": {
"query": {
"page": 1,
"limit": 10
}
}
}'
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Commands
List published post summaries — ghostcontent.posts.list
Read one page of published post identities, titles, URLs and excerpts. Rich HTML, code injection and author payloads are not requested. This is the Content API, separate from the Admin API.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
query |
object | Required | additionalProperties: false |
|
query.page |
integer | Required | One-based page. | minimum: 1; maximum: 9007199254740991 |
query.limit |
integer | Required | Items per page, maximum 100. | minimum: 1; maximum: 100 |
Full JSON Schema
Example input
{
"query": {
"page": 1,
"limit": 10
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Read a published post summary — ghostcontent.posts.get
Read one known published post identity, title, URL and excerpt using a Content API key. Rich body content, memberships and Admin API actions are outside this subset.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
path |
object | Required | additionalProperties: false |
|
path.id |
string | Required | Known 24-character hexadecimal post ID. | pattern: "^[a-fA-F0-9]{24}$" |
Full JSON Schema
Example input
{
"path": {
"id": "5c7e8b4f60a14b10770ff72a"
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Errors
Check the key's expiry, revocation, workspace and allowed operations.
Reuse the same idempotency key only for the same request.
The connection or provider limit has been reached. Check the receipt before retrying.
Test the connection
Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.