Skip to main content
Glama

Create a post draft

flypost_create_draft

Create a draft: pass content_bank_item_id to draft from a developed concept (reuses an existing draft when one exists), or pass text (or nothing) for a free-form post. For agent-authored posts, write the text yourself grounded on flypost_get_writing_voice + flypost_search_brain.

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": "flypost_create_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoInitial post text for a free-form draft.
agent_nameNoYour name (e.g. 'Claude') — shown in the post's Sources panel as the author.
project_idNoProject id; omit for the active project.
authoring_noteNoOne or two sentences on where this post's material came from (conversation context, documents you read, data you verified). Shown to the user in the post's Sources panel — always provide it when you wrote the words.
content_bank_item_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the description's job is to add behavioral detail, and it does: the non-obvious disclosure that a concept-based call reuses an existing draft when one exists. It still omits what is returned (e.g. a draft id) and any permission or error behavior, so it is not fully transparent.

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?

Two sentences, front-loaded with the core verb and the mode split, with every clause carrying information. The parenthetical '(or nothing)' and stacked clauses make it slightly denser than it needs to be, but nothing 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?

For a zero-required-parameter creation tool with no output schema, the description covers the branching logic and prerequisites an agent needs to call it correctly. The main gap is that it never indicates what a successful call yields, which the absence of an output schema makes worth stating.

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 80%, so the baseline is 3, and the description goes beyond it by explaining the content_bank_item_id-vs-text branching and that text may legitimately be omitted. It adds no extra meaning for agent_name, authoring_note, or project_id, but the schema already documents those well.

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 gives a specific verb+resource (create a draft) and enumerates its two creation modes: concept-based via content_bank_item_id or free-form via text/nothing. It does not name a sibling such as flypost_generate_post_draft, so an agent cannot fully disambiguate between the two draft-producing tools from this text alone.

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?

It clearly states which parameter selects which mode, and prescribes prerequisites for agent-authored posts by pointing at flypost_get_writing_voice and flypost_search_brain. There is no explicit 'do not use this when…' exclusion or a stated alternative tool for the generate-a-draft path, which keeps it below a 5.

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.