Skip to main content
Glama

Generate an AI image for a carousel slide

flypost_generate_slide_image

Generate an AI image for one slide of a template carousel (blocks 1-4 minutes). It becomes the slide's image; the one it replaces stays in the slide's history (flypost_reuse_slide_image puts it back). After the last slide, check the deck with flypost_view_visuals and give the user the editor_url. Never render the PDF to check the slides. Not for a Designed layout deck: change that with 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>",
      "slide_id": "<slide_id>"
    },
    "name": "flypost_generate_slide_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
slide_idYesFrom the item's content.slides, or flypost_view_visuals.
colour_modeNoColour handling; defaults to 'brand' — the user's brand palette.
image_promptNoCustom image prompt; omit to let the app decide from the slide.
carousel_image_styleNoVisual style key; defaults to minimal_geo_collage (brand-colour aware).
content_bank_item_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), it discloses operation latency (blocks 1-4 minutes), the reversibility model (the replaced image stays in slide history and can be restored), and the required post-call verification step. That is meaningful behavioral context the agent cannot get from the schema or hints.

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?

Opens with the core action and scope, then layers alternatives, side effects, and follow-up in short declarative sentences with no filler. Every sentence carries an operational constraint or a routing decision.

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 mutating, slow, non-read-only tool with no output schema, the definition covers the latency, reversibility, alternatives, and the exact verification and handoff steps (view visuals plus editor_url). Nothing an agent needs to call this correctly and follow up properly 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 description coverage is already 80% with defaults and an enum documented inline, so the schema does most of the work. The description adds only indirect hints ('template carousel', slide history) and no syntax or format detail for image_prompt or carousel_image_style beyond what the schema says, so 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 ('Generate an AI image for one slide of a template carousel') and scopes it to template carousels, distinguishing it from flypost_revise_design for Designed layout decks and from flypost_generate_image. An agent can identify the target artifact from the description alone.

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?

Gives explicit exclusions and alternatives: not for Designed layout decks, use flypost_revise_design; restore a previous image with flypost_reuse_slide_image; verify the deck afterward with flypost_view_visuals. It also names an anti-pattern ('Never render the PDF to check the slides'), which is exactly the kind of routing guidance agents need.

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.