Skip to main content
Glama

Reuse a slide image on a carousel slide

flypost_reuse_slide_image

Put an image that was already on a carousel slide (this carousel or another one, current or from its history) onto one slide of this carousel, keeping its crop. Also how to revert a slide to an earlier image. Any image it replaces stays in the slide's history.

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>",
      "source_url": "<source_url>"
    },
    "name": "flypost_reuse_slide_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
slide_idYesFrom the item's content.slides, or flypost_view_visuals.
source_urlYesThe slide image url (current or from its history), e.g. from flypost_view_visuals or flypost_list_media.
content_bank_item_idYes
source_content_bank_item_idNoThe carousel the image comes from, when it is not this one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare it is not read-only, not destructive, and not open-world. The description adds meaningful context beyond that: the existing crop is kept and any replaced image remains in the slide's history, which explains the practical meaning of non-destructive behavior for this mutation.

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?

Two front-loaded sentences with little waste. The second sentence ('Also how to revert a slide to an earlier image') is slightly loosely attached but still earns its place by naming a second use case.

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?

For a four-parameter mutation tool with no output schema, the description covers the key behavioral facts: cross-carousel and historical sources, crop retention, and history retention on replace. It does not explain the return value or confirmation behavior, but that is a minor gap given the annotations.

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 75%, so the schema already documents most parameters including source_url and source_content_bank_item_id. The description reinforces that the source can be current or historical and can come from another carousel, but adds no syntax or format detail beyond the schema.

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?

States a specific verb+resource ('Put an image ... onto one slide of this carousel') and clarifies the source may be this carousel, another carousel, or history. It stops short of distinguishing itself from close siblings like flypost_copy_slide_image or flypost_move_slide_image, so an agent may still hesitate between them.

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?

The description implies when to use it (reusing an existing slide image while preserving crop) and mentions the revert use case, but gives no explicit exclusions or guidance on when a sibling such as copy or move would be the better choice.

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.