Skip to main content
Glama

Update draft text (agent-authored)

flypost_update_draft
Idempotent

Replace a draft's post text — the autosave-equivalent edit. This REPLACES existing text; the result includes previous_text so you can restore it if the overwrite was a mistake. Follow the project writing voice (flypost_get_writing_voice). Line breaks are preserved as LinkedIn paragraphs.

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>",
      "text": "<text>"
    },
    "name": "flypost_update_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe full post text (plain text, line breaks preserved).
draft_idYes
agent_nameNoYour name (e.g. 'Claude') — shown in the post's Sources panel as the author.
authoring_noteNoOne or two sentences on where this text's material came from. Shown to the user in the post's Sources panel — always provide it when you wrote the words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=false and idempotentHint=true; the description adds the crucial caveat that the edit overwrites existing text and that the response echoes previous_text for restoration — exactly the recoverability detail an agent needs before overwriting. It does not cover side effects on scheduled posts or draft versioning, which keeps it below 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?

Three short sentences, front-loaded with the destructive-overwrite warning in caps, then the recovery path, then the cross-reference. Every sentence carries information an agent needs before calling.

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 usefully discloses the previous_text return field, and it addresses the main risk of a mutation tool. Minor gaps remain around draft state after the edit and interaction with scheduled publishing.

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 75%, so agent_name and authoring_note are already explained in the schema. The description still adds meaning by clarifying LinkedIn paragraph behavior for line breaks, which goes beyond the schema's terse "line breaks preserved" note.

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?

"Replace a draft's post text" names a specific verb and resource, and "the autosave-equivalent edit" frames it against create_draft and generate_post_draft, which are the siblings an agent might otherwise confuse it with. No ambiguity about what the tool does.

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 establishes context (editing existing draft text rather than creating one) and points to flypost_get_writing_voice as a prerequisite step for voice consistency. It stops short of an explicit "when not to use / use X instead" routing sentence, but the alternative is clearly implied by "Replace".

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.