Skip to main content
Glama

Generate post copy (server pipeline)

flypost_generate_post_draft
Destructive

Run Flypost's tuned draft writer for a draft (grounded on its concept, the Brain, and the brand voice). Pass feedback to refine the current text instead of writing fresh. Blocks until ready (typically 1-2 minutes).

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

Input Schema

NameRequiredDescriptionDefault
draft_idYes
feedbackNoImprovement feedback — refines the existing draft text rather than rewriting from scratch.
post_styleNoOptional named post style.
notebook_idNoGround the write on one notebook.
freeform_promptNoFor free-form drafts: the topic/prompt to write about.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The valuable addition beyond annotations is the blocking, synchronous nature and typical 1-2 minute latency, which annotations cannot convey. However, annotations declare destructiveHint=true, and the description never says that regenerating replaces/overwrites the draft's existing copy — an agent could reasonably assume it only appends or previews.

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?

Three short sentences with the core action front-loaded and no filler. The latency note earns its place; the parenthetical about grounding could be compressed slightly but is not wasteful.

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?

There is no output schema, so the description should say what comes back or what state the draft ends in after the call; it does not. For a long-running, destructive write it covers latency and inputs adequately but leaves the post-call state and overwrite semantics unstated.

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 80%, so most parameters are already documented, and the description's feedback sentence largely restates the schema's own 'refines the existing draft text rather than rewriting from scratch'. The aside that grounding draws on concept, Brain and brand voice adds modest context for the otherwise undocumented notebook_id/prompt grounding.

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 states a specific verb and resource: run the tuned draft writer for a given draft, grounded on concept, Brain and brand voice. That is clearly distinct from create_draft, update_draft or generate_article, though it never names those siblings as alternatives.

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?

It gives one concrete usage rule — pass feedback to refine the existing text rather than writing fresh — which resolves the main ambiguity in how to call it. It offers no routing guidance against sibling tools (e.g. when to create a new draft vs. regenerate this one, or when to use generate_article instead).

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.