Skip to main content
Glama

ghost_list_pages

Read-onlyIdempotent

Retrieve pages from a Ghost site using its site URL and Content API key, with an optional limit to control how many pages are returned.

Instructions

List Ghost pages.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site_url": "<site_url>",
      "content_key": "<content_key>"
    },
    "name": "ghost_list_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPages to return (max 100, default 15)
site_urlYesGhost site URL
content_keyYesGhost Content API key

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

C2.8/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so safety is fully covered. The description adds nothing beyond that: no pagination behavior, no mention that content_key is required for the call to succeed, no note on what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with zero waste and the resource front-loaded, but it is under-specified rather than efficient - there was room for a clause about scope or filtering at no cost to brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool requiring a site URL and Content API key, the description says nothing about auth prerequisites, pagination, or return shape (no output schema exists). Annotations and schema carry most of the load, but the definition is still thin for a real integration call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, documenting limit (max 100, default 15), site_url, and content_key. The description adds no meaning beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List Ghost pages'), and the resource noun 'pages' distinguishes it from ghost_list_posts and ghost_list_tags by name. It doesn't explicitly call out the sibling relationship, but an agent can tell what it returns without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no exclusions, and no mention of the alternative ghost_list_posts or pagination behavior. The agent must infer everything from the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools