Skip to main content
Glama

list_drafts

Read-only

List posts by publishing status, newest first. Defaults to drafts. Each post comes with its id, copy, channels, tags, editorial stage, schedule if any, and who it is waiting on if it is under review. Returns up to limit posts (default 20, max 100); there is no paging. Use this to find a post's id before get_post, update_draft or schedule_post. For "what's going out and when", use list_scheduled_posts instead, which shows posts by their send time and includes any that missed their time. For "what did I post", use list_recent_posts. For posts someone asked you to review, use list_posts_awaiting_my_review.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_drafts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax posts to return (default: 20, max: 100)
statusNoFilter by publishing status (default: draft)
workspaceNoOptional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.
editorial_statusNoFilter by editorial workflow stage (needs_writing, drafting, internal_review, client_review, revision_requested, on_hold, ready_to_schedule, rejected, done)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspace
      Added value: +{
      +  "description": "Optional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already establish read-only and non-destructive, yet the description still adds real behavior: the composition of each returned post, the limit cap with default 20 and max 100, and the significant constraint that there is no paging. That no-paging fact is exactly the kind of thing an agent cannot learn from annotations or schema and would otherwise discover only by trial.

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

Conciseness4/5

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

Front-loaded with purpose, default, and return shape, followed by routing rules ordered by likely confusion. The three routing sentences are slightly repetitive in phrasing ("For X, use Y instead") but each carries distinct information, so nothing is truly wasted.

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

Completeness5/5

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

With no output schema, the description correctly compensates by enumerating the fields of each returned post and stating the result count behavior and absence of paging. For a four-optional-parameter read tool, an agent has everything needed to call it and interpret results correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description still adds the default-to-drafts behavior and the 20/100 limit bounds, reinforcing the two most easily misused parameters. It does not elaborate on workspace or editorial_status beyond what the enum schema already spells out, so it is above baseline but not comprehensive.

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

Purpose5/5

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

The description opens with a specific verb and resource plus ordering ("List posts by publishing status, newest first") and immediately states the default scope ("Defaults to drafts"). It then names four sibling tools it is not, so an agent can distinguish it from list_scheduled_posts, list_recent_posts, and list_posts_awaiting_my_review without opening any schema.

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

Usage Guidelines5/5

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

It gives explicit when-to-use guidance ("find a post's id before get_post, update_draft or schedule_post") and explicit when-not-to-use routing for three alternatives, each with the condition that selects it (send time, already posted, awaiting my review). This is textbook alternative disambiguation.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources