Skip to main content
Glama

Rewrite the words on an image

flypost_refine_image_copy
Destructive

Have the app rewrite the words on an Image or infographic post from your feedback (the editor's "Edit text" on the image): headline, stat, comparison rows, steps or list items. It saves the new copy to the concept; the picture changes only when you generate again with flypost_generate_image (same variant), so read the returned copy first. An Image post's reply carries the fact-check's warnings: pass them to the user rather than generating over them. To set the words exactly yourself, resave with flypost_save_concept (image_copy / infographic_copy). Carousel slides: flypost_edit_slides. Designed layouts: flypost_revise_design.

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": {
      "content_bank_item_id": "<content_bank_item_id>",
      "feedback": "<feedback>"
    },
    "name": "flypost_refine_image_copy"
  }
}

Input Schema

NameRequiredDescriptionDefault
feedbackYesWhat to change, e.g. "make the stat about time saved, not cost".
content_bank_item_idYes

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?

The description goes well beyond the annotations by explaining the two-phase behavior (copy saved now, picture only changes on a later generate call) and by requiring fact-check warnings to be surfaced to the user rather than generated over. It never explicitly says the previously stored copy is overwritten, which is the main thing an agent needs to know given destructiveHint=true.

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 action, then consequences, then a compact set of sibling routing clauses. It is dense but every sentence carries information; the parenthetical "(the editor's \"Edit text\" on the image)" is the only slightly expendable phrase.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation tool with no output schema, the definition covers the lifecycle (save, then regenerate), the return surface ('read the returned copy first', 'reply carries the fact-check's warnings'), and all sibling boundaries. Nothing an agent needs before calling is missing.

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%: 'feedback' is documented in the schema, but 'content_bank_item_id' has no description anywhere. The description reinforces what feedback should contain ('from your feedback', 'what to change') but adds nothing about identifying the target concept, so it only partly compensates for the coverage gap.

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?

States a specific verb and resource ('rewrite the words on an Image or infographic post') and enumerates the affected copy blocks (headline, stat, comparison rows, steps, list items). It is immediately distinguishable from siblings because it names four of them by role.

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

Usage Guidelines5/5

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

Explicitly routes the agent: exact wording goes to flypost_save_concept, carousel slides to flypost_edit_slides, designed layouts to flypost_revise_design, and re-rendering to flypost_generate_image with the same variant. Each alternative comes with the condition that selects it.

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.