Skip to main content
Glama

Preview Carousel

carousels_preview
DestructiveIdempotent

Render and store private JPEG previews for the selected carousel slides. Replaces cached previews at deterministic storage keys; preserves the source project and slide document.

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>",
      "chrome": "<chrome>"
    },
    "name": "carousels_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
chromeYesnone
projectIdYesUUID string.
workspaceIdNo
slideIndexesNo
idempotencyKeyYes

Output Schema

NameRequiredDescriptionDefault
frameYes
slidesYes
platformYes
revisionYes
warningsYes
project_idYes
next_actionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / slides / items / properties / print / enum
      Previous value: -[
      -  "slots",
      -  "ingested"
      -]New value: +[
      +  "slots",
      +  "ingested",
      +  "board"
      +]
  2. Changed2 schema fields changed
    • addedInput schema / properties / idempotencyKey
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 200,
      +      "minLength": 8,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
    • changedInput schema / required
      Previous value: -[
      -  "projectId",
      -  "chrome"
      -]New value: +[
      +  "idempotencyKey",
      +  "projectId",
      +  "chrome"
      +]
  3. Added

TDQS

B3.3/5.0
Behavior4/5

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

This is the description's real strength. It goes beyond the annotations by disclosing that previews are written to deterministic storage keys, that cached previews are replaced, and that the source project and slide document are preserved — directly clarifying the blast radius implied by destructiveHint=true. It still omits permission requirements and any size/cost limits, keeping it at 4.

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 compact sentences with no filler, and the highest-value content (what gets replaced, what is preserved) sits in the second sentence before any drift. Nothing here is redundant.

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?

The output schema means return values need not be explained, and the destructive/idempotent profile is well covered. However, for a 5-parameter, 3-required tool with 20% schema coverage and ambiguous fields like chrome and idempotencyKey, the description is too thin to let an agent invoke it confidently without guessing.

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 20% — just projectId carries 'UUID string.' — yet the description never mentions idempotencyKey, chrome, workspaceId, or slideIndexes. 'Selected carousel slides' is the only faint gesture toward slideIndexes, giving no rule for what an omitted or empty array does, which matters for a 5-parameter write tool.

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 uses a specific verb pair ("Render and store") with a clear resource ("private JPEG previews for the selected carousel slides"), which is enough to distinguish it from mutation siblings like carousels_patch_slide or carousels_compile. It stops short of naming a related sibling such as carousels_get or media_assets_preview, so a 4 rather than a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance is given: nothing says whether this must be called before sharing, whether it is a prerequisite for another step, or how it relates to carousels_get or the other *_preview tools. The agent is left to infer the workflow position entirely.

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