Skip to main content
Glama

Copy a carousel slide image onto another slide

flypost_copy_slide_image

Copy a slide's image onto another slide of the same carousel; the source keeps it, and the target's old image stays in its history. 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_copy_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

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description adds real context: the source image is retained, the target's previous image lands in history, and the crop is preserved on copy. That history-retention detail is the key non-obvious behavior for a mutation tool. It omits any permission or failure conditions, which keeps it below a 5.

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 compact sentences with the core action front-loaded and the retention/verification details following. Nothing is redundant, though the semicolon-chained clauses are dense enough to require a second read.

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

Completeness3/5

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

No output schema exists and three required parameters have zero schema descriptions, so the description must do more than it does. It covers the copy semantics and verification path well but leaves the content_bank_item_id requirement and the return shape for the agent to guess.

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 the roles of from_slide_id and to_slide_id (source retained, target overwritten into history) and points to flypost_view_visuals for obtaining ids, but content_bank_item_id goes entirely unexplained in both schema and description.

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 and resource: copy a slide's image onto another slide of the same carousel. The 'copy' framing and the 'source keeps it' clause implicitly distinguish it from siblings like flypost_move_slide_image and flypost_swap_slide_images, though those alternatives are never named.

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?

Provides concrete workflow guidance: slide ids come from flypost_view_visuals and the result should be verified there afterwards. It does not say when to prefer this over swap or move siblings, so the agent must infer the choice from the verb alone.

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.