Skip to main content
Glama

Get a post draft

flypost_get_draft
Read-only

Read one post draft: text, status, authenticity score, publish state — plus the backing concept's visual state (carousel PDF, selected image, editor link) when the draft is concept-backed.

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

Input Schema

NameRequiredDescriptionDefault
draft_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare this a safe, closed-world read, so the description's added value is the disclosure of the conditional payload: concept-backed drafts also return carousel PDF, selected image, and editor link. That is a genuine behavioral trait beyond the annotations. It omits what happens for a missing or non-existent draft_id, which keeps it from a 5.

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 the action first and the return payload second; every clause earns its place, and the em-dash conditional is an efficient way to express shape variation.

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 must describe the return value, and it does so at a useful level of detail including the conditional branch. Combined with readOnly/openWorld annotations, an agent has enough to call this correctly; only error behavior and ID provenance remain unstated.

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

Parameters2/5

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

Schema description coverage is 0% for the single parameter, so the description carries the full burden of explaining draft_id — and it says nothing about its format, source, or whether it comes from a list call or a create response. 'Read one post draft' only weakly implies an identifier key.

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 opens with a specific verb and resource ('Read one post draft') and enumerates the returned fields (text, status, authenticity score, publish state), which clearly separates it from mutation siblings like flypost_create_draft and flypost_update_draft. It does not explicitly name an alternative, so it stops just short of full sibling differentiation.

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

Usage Guidelines3/5

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

Usage is implied: fetch a single draft by ID, with a conditional note that concept-backed visual state is included when applicable. There is no explicit when-to-use/when-not guidance and no pointer to a list or search alternative for discovering draft IDs.

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.