Skip to main content
Glama

Generate article infographic (server pipeline)

flypost_generate_article_infographic

Turn one passage of a Pulse article into a branded infographic image (the editor's "Create infographic" flow). The server creates a hidden content bank item and runs the art-director + image pipeline; this blocks until the image is ready (typically 1-4 minutes). Returns the finished image urls plus the content_bank_item_id and editor_url — hand editor_url to the user so they can see the graphic in place in the article.

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": {
      "article_id": "<article_id>",
      "text": "<text>"
    },
    "name": "flypost_generate_article_infographic"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe exact passage to visualise (the app requires at least ~180 characters).
styleNoInfographic layout family; defaults to stats.
article_idYes
aspect_ratioNoOmit to let the pipeline choose a compatible ratio.
include_logoNoStamp the brand logo. Defaults to false — inline article graphics omit it.
image_workflowNoImage model to render with. Omit to use the default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare it is non-read-only, non-destructive and closed-world; the description goes far beyond by disclosing the hidden content bank item side effect, the art-director + image pipeline, a 1-4 minute blocking wait, and the exact return payload. Blocking duration and hidden-state creation are exactly the facts an agent cannot get from annotations.

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 sentences, front-loaded with what the tool does, then the blocking behavior, then the return value and the required follow-up action. Every sentence carries information an agent needs; there is no filler.

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?

With no output schema, the description compensates by enumerating the return values (image urls, content_bank_item_id, editor_url) and prescribing what to do with them. It also covers the blocking latency, which is critical for a long-running generation call.

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 description coverage is 83%, and the schema already documents text length, style/aspect_ratio defaults, include_logo semantics and image_workflow. The description reinforces 'one passage' but adds no new per-parameter meaning, so the baseline 3 applies.

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 with scope: 'Turn one passage of a Pulse article into a branded infographic image.' The reference to the editor's 'Create infographic' flow anchors it to a concrete UI action, letting an agent distinguish it from sibling image tools such as article cover or generic image generation.

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?

The description establishes the usage context (a single article passage, inside the article editor flow) and tells the agent to hand editor_url back to the user. It does not explicitly exclude alternatives like flypost_generate_article_cover or flypost_generate_image, so routing between image tools still requires inference.

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.