Skip to main content
Glama

ghost_list_posts

Read-onlyIdempotent

Retrieve published Ghost posts using a site URL and Content API key, with optional limit and filter parameters to control results.

Instructions

List published Ghost posts.

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_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPosts to return (max 100, default 15)
filterNoGhost filter (e.g. tag:news)
site_urlYesGhost site URL
content_keyYesGhost Content API key

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The word 'published' adds real value by implying drafts are never returned, but nothing is said about pagination limits or how filtering behaves across pages.

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

Conciseness5/5

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

A single front-loaded sentence with zero filler; the scope qualifier 'published' comes before any noun the agent might misread. Nothing redundant is included.

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

Completeness3/5

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

For a simple read-only list tool with full schema coverage and safety annotations, the core is covered. The gaps are the absence of sibling differentiation and any hint about result volume/paging behavior given the default limit of 15.

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%, with limit (max 100, default 15), filter syntax example, site_url and content_key all documented in the schema. The description adds no parameter meaning beyond that, so the baseline of 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 posts') plus a scope qualifier ('published'), so the agent knows drafts are excluded. However, it does not distinguish itself from siblings such as ghost_list_pages or ghost_list_tags, which an agent could easily confuse with a post listing.

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?

There is no guidance on when to use this versus ghost_list_pages, ghost_list_tags, or the similarly named wordpress_list_posts / jp_list_posts siblings. No prerequisites (e.g., that a Content API key is required rather than an Admin key) are mentioned either.

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