Skip to main content
Glama

Edit Carousel Board

carousels_board_edit
DestructiveIdempotent

Apply ordered operations to a carousel board by slide and element ID: add a slide from a template with its text and photos, change text and style, insert, duplicate, move or remove slides, set the theme, apply the brand or a saved theme, hide or lock an element. Operations apply to the latest board unless expectedRevision is set; dryRun saves nothing. Returns the base and new revision, affected IDs, slide order and a summary of each changed slide; errors name the failing operation. Identical idempotency keys replay.

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": {
      "idempotencyKey": "<idempotencyKey>",
      "projectId": "<projectId>",
      "operations": "<operations>"
    },
    "name": "carousels_board_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
dryRunNoApply to the latest board without saving and return the would-be result.
projectIdYesUUID string.
operationsYes
workspaceIdNoUUID string.
idempotencyKeyYes
expectedRevisionNoNull (default) applies the operations to the latest board. A revision rejects the edit with a conflict when the board has moved.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructive=true and idempotentHint=true, but the description adds real behavior beyond them: optimistic concurrency via expectedRevision with conflict rejection, dryRun as a no-save preview, errors that name the failing operation, and idempotency-key replay semantics. The one weak spot is the return-value sentence, which largely restates what the existing output schema already covers.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences are well front-loaded with scope, revision and dryRun behavior. The long middle enumeration of per-operation payloads is a dense run-on that substantially overlaps the operations schema description, so a meaningful share of the text does not earn its place. It is informative but not tight.

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 high-complexity, 12-kind batch mutation tool this covers the essentials: concurrency, dry run, idempotency, error attribution and affected-ID reporting, with an output schema handling return shape. What is missing is any guidance on ordering pitfalls or partial-failure behavior when one operation in the ordered list fails.

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 67% and the operations parameter already carries a long inline description, so the description risks duplicating it. Where it genuinely adds meaning is in behavioral rules the schema does not state: style values of null remove an override, photos should be swapped via src on the image element rather than rebuilding the slide, and an omitted hidden/locked flag keeps prior state. Those are semantic constraints an agent would otherwise get wrong.

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?

Opens with a specific verb and resource: 'Apply ordered operations to a carousel board by slide and element ID', then enumerates the concrete operation families (slides, text/style, theme, hide/lock). An agent can tell this is a batch mutation endpoint rather than a read or generate tool. It does not name any sibling, so differentiation from tools like carousels_patch_slide or editor_composition_edit is left to inference.

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?

Useful context is given for two modifiers: operations hit the latest board unless expectedRevision is set (which yields a conflict), and dryRun saves nothing. However there is no explicit when-to-use-this-vs-alternatives guidance, and no statement about when an agent should prefer the single-purpose sibling tools over this batch endpoint. Usage is implied by capability rather than stated.

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