Skip to main content
Glama

update_carousel_slides

Idempotent

Change the text (hook and/or bullets) of one or more slides — for the user's own wording, or rewrites they asked you for. Omit a field to keep it.

Only text changes here: a slide that already has an image keeps showing the old text until it is redrawn with generate_carousel_slides(slide_numbers=…).

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>",
      "slides": "<slides>"
    },
    "name": "update_carousel_slides"
  }
}

Input Schema

NameRequiredDescriptionDefault
slidesYes
carousel_idYes
workspace_idYes

Output Schema

NameRequiredDescriptionDefault
noteNo
topicYes
slidesYes
statusYes
theme_keyNo
created_atYes
theme_nameNo
updated_atYes
carousel_idYes
slides_needing_imagesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly=false, destructive=false, idempotent=true), so the description adds real value by disclosing the non-obvious caveat that imaged slides keep rendering stale text until regenerated. That is exactly the kind of behavior an agent needs before calling.

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?

Three short sentences, front-loaded with the action and scope, then the alternative, then the caveat. Minimal waste, though the parenthetical '(hook and/or bullets)' is slightly redundant with the schema.

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?

Complete for a small mutation tool: behavior, field omission semantics, and the follow-up action are all stated, and an output schema exists so return values need not be described. Minor gaps (slide number validity, whether the carousel must be in a draft state) do not block correct invocation.

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

Parameters4/5

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

Schema coverage is 0%, so the description must carry parameter meaning — and it does, defining hook/bullets as the text fields and clarifying that omitting a field means 'keep current value', which disambiguates the schema's bare null defaults. It does not explain the slides[].num identifier or bullet item semantics, which keeps it from a 5.

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?

The description names a specific verb and resource ('Change the text (hook and/or bullets) of one or more slides') and scopes it to text-only edits. It clearly signals the boundary against generate_carousel_slides for redrawing, though it does not differentiate from the sibling edit_carousel_slide.

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?

It gives explicit when-to-use context ('for the user's own wording, or rewrites they asked you for') and names the alternative plus condition when a redraw is required. It lacks an explicit exclusion against other slide-editing siblings, but the core routing is present.

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