Skip to main content
Glama

Read one draft in full

get_content_draft
Read-only

One draft with everything needed to iterate on it: text, media, the post it quotes, schedule state, the reviewer's per-axis breakdown, the score before the last rewrite, and its earlier versions (newest first). FREE. Each version has a version_id — pass it to revise_content_draft action:"restore" to bring that text back (e.g. "the first hook was better"). locked:true means it is already scheduled or live: do not try to change it; tell the user where to change it (locked_reason).

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": {
      "space_id": "<space_id>",
      "draft_id": "<draft_id>"
    },
    "name": "get_content_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
draft_idYesFrom get_content_queue.
space_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only cover readOnlyHint and openWorldHint, and the description layers on genuinely non-obvious behavior: the call is FREE, versions are returned newest-first, and locked drafts are immutable with a locked_reason pointer. It doesn't mention size or volume limits on the version history or whether all versions are returned, which is the remaining behavioral gap for a tool whose payload is unbounded.

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 the payload inventory, then the restore workflow, then the lock warning — the ordering matches what an agent needs to decide and act. The single dense paragraph is a bit run-on and mixes three topics, but no clause is filler.

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

Completeness4/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 carries the return-shape burden and does so well by enumerating the fields and their ordering. The two remaining holes — space_id semantics and version-list bounds — keep it from being fully self-sufficient for a read tool with a potentially large nested payload.

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 coverage is 50% — draft_id is documented as coming from get_content_queue, but space_id is not described in either the schema or the description, and the description does nothing to compensate for it. The description's only parameter talk concerns version_id, a field of a different tool's input, so baseline 3 is the right ceiling.

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?

The description immediately enumerates exactly what a single draft fetch returns — text, media, quoted post, schedule state, reviewer per-axis breakdown, prior score, and version history newest-first — which makes the singular-retrieval scope unmistakable versus a listing tool like get_content_queue. It stops short of a clean verb-first statement (the verb lives only in the title) and never names a sibling to contrast with, so it is clear but not fully differentiated on its own.

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

Usage Guidelines4/5

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

Strong conditional guidance: locked:true means scheduled or live, do not attempt changes, and redirect the user via locked_reason; and version_id is routed to revise_content_draft action:"restore" with a concrete example. It lacks an explicit 'use this instead of X' statement for the read path (e.g. queue vs single draft) and doesn't state prerequisites for space_id, so no exclusions are spelled out.

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.