Skip to main content
Glama

Remove a carousel slide's image

flypost_remove_slide_image
Destructive

Take the image off one carousel slide, leaving it without one (an image-led template then shows that slide bare). Only when the user asks, or to make a slide text-only.

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_remove_slide_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
slide_idYesFrom the item's content.slides, or flypost_view_visuals.
content_bank_item_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds useful consequence detail ('leaving it without one', an image-led template then shows that slide bare), but says nothing about whether the removed image is recoverable or what happens to any stored asset, which matters for a destructive operation.

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?

Two short sentences with the action and scope front-loaded, then the downstream consequence in a parenthetical. Nothing is redundant and every clause carries information.

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?

For a simple two-parameter mutation whose annotations already flag destructiveness, the description covers purpose, consequence, and usage conditions. It still leaves the undocumented content_bank_item_id and the reversibility of the removal unaddressed, which are the main remaining gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%: slide_id is documented but content_bank_item_id has no description in either schema or description. The phrase 'one carousel slide' hints at slide_id, but the description never explains the item identifier or how the two parameters relate, so it does not compensate for the coverage gap.

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 ('take the image off one carousel slide') and scopes it to a single slide, which implicitly separates it from the post-level flypost_remove_post_image. It does not explicitly name an alternative, so it stops just short of full sibling differentiation.

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?

Provides a clear when-to-use rule ('Only when the user asks, or to make a slide text-only'), which also functions as a do-not-use-unprompted guardrail. It does not point to any alternative tool for related image changes such as moving, swapping, or replacing the image.

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.