Skip to main content
Glama

edit_carousel_slide

Change one finished slide image with a plain-language instruction ("make the title bigger", "swap the laptop for a phone", "fix the typo in the second point"). The rest of the image is kept. Uses one image credit.

The new image becomes the slide's current one; earlier versions are kept so the user can step back in reeldrop's Carousel Lab. To change the slide's TEXT wholesale, prefer update_carousel_slides + generate_carousel_slides with slide_numbers=[n] — a redraw follows the theme more faithfully than an edit.

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": {
      "workspace_id": "<workspace_id>",
      "carousel_id": "<carousel_id>",
      "slide_num": "<slide_num>",
      "instruction": "<instruction>"
    },
    "name": "edit_carousel_slide"
  }
}

Input Schema

NameRequiredDescriptionDefault
slide_numYes
carousel_idYes
instructionYes
workspace_idYes

Output Schema

NameRequiredDescriptionDefault
image_urlYes
slide_numYes
carousel_idYes
version_countYes
image_credits_leftNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly=false, destructive=false, openWorld=true, idempotent=false). The description adds context beyond them: the operation consumes one image credit, only the targeted element changes while the rest is preserved, the new image supersedes the current one, and earlier versions remain recoverable in Carousel Lab. That is exactly the cost and reversibility information an agent needs before invoking a non-idempotent 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?

Front-loaded with the core action and examples, then cost/state behavior, then the alternative — a sensible order. Slightly padded ('The new image becomes the slide's current one; earlier versions are kept so the user can step back in reeldrop's Carousel Lab' could be tighter), but every sentence carries information an agent would otherwise have to guess.

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?

An output schema exists, so return values need no explanation, and the description covers cost, reversibility, partial-edit semantics, and the escape hatch to regeneration. The remaining hole is parameter-level detail for the identifiers, which is the main thing an agent could still get wrong.

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 0% across four required parameters, so the description must carry the burden. It clarifies 'instruction' well through examples, but workspace_id, carousel_id, and slide_num get no explanation at all — notably no hint about whether slide_num is 0- or 1-based, which matters for a per-slide edit. Three of four parameters remain undocumented in both structured fields and prose.

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 ('Change one finished slide image with a plain-language instruction') and scopes it precisely ('The rest of the image is kept'). Three concrete instruction examples make the input shape unambiguous, and the description explicitly contrasts itself with the regenerate path, so an agent can differentiate without opening the 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?

Gives an explicit when-to-use rule and a named alternative with the exact call shape: wholesale text changes should go to update_carousel_slides + generate_carousel_slides with slide_numbers=[n]. It also explains why the alternative is better ('a redraw follows the theme more faithfully than an edit'), which is real routing guidance rather than a bare pointer.

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.

Resources