Skip to main content
Glama

Move a carousel slide image to another slide

flypost_move_slide_image
Destructive

Move a slide's image to another slide of the same carousel; the source slide is left without an image. To exchange two slides' images use flypost_swap_slide_images. The image keeps its crop. Slide ids come from flypost_view_visuals; check the result there afterwards.

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>",
      "from_slide_id": "<from_slide_id>",
      "to_slide_id": "<to_slide_id>"
    },
    "name": "flypost_move_slide_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
to_slide_idYes
from_slide_idYes
content_bank_item_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, and the description earns extra credit by explaining exactly what is destroyed: the source slide is left without an image. It further discloses that the image keeps its crop, which is non-obvious state behavior, and prescribes a verification step in flypost_view_visuals.

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?

The destructive consequence and the swap alternative are front-loaded, and every clause adds decision-relevant information (negative outcome, alternative routing, crop preservation, id source, verification). No redundant restatement of the title.

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 3-parameter mutation with no output schema, the description covers the destructive effect, the alternative tool, id provenance, and where to verify afterwards. It does not state what the tool itself returns (e.g., confirmation payload), though the pointer to flypost_view_visuals largely compensates.

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 0%, so the description carries the burden: it clarifies that from_slide_id/to_slide_id are slide ids sourced from flypost_view_visuals and must belong to the same carousel. However, content_bank_item_id is never explained — only implied by 'same carousel' — leaving one of three required parameters without added meaning.

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 ('Move a slide's image') restricted to 'another slide of the same carousel', and immediately distinguishes itself from the swap sibling. An agent can differentiate this from flypost_swap_slide_images and flypost_copy_slide_image without opening any schema.

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 names the alternative (flypost_swap_slide_images) and the condition that selects it ('To exchange two slides' images'). It also routes the agent to flypost_view_visuals for retrieving slide ids and for post-call verification, which is concrete when-to-use guidance.

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.