Skip to main content
Glama

List Carousel Board Versions

carousels_board_versions
Read-onlyIdempotent

List saved versions of a carousel board, newest first (revision, source: baseline, editor, agent, api, generation or restore; author, merged change count, slide count), or with versionId read one version as a board summary. Saves by the same author and source within three minutes share one version; the newest 50 are kept.

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": {
      "projectId": "<projectId>",
      "versionId": "<versionId>",
      "view": "<view>",
      "limit": "<limit>"
    },
    "name": "carousels_board_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewYessummary
limitYes
projectIdYesUUID string.
versionIdYes
workspaceIdNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely behavioral facts beyond that: ordering is newest-first, saves by the same author and source within three minutes collapse into one version, and only the newest 50 versions are retained. The field list mostly restates what the output schema should contain, which tempers it slightly.

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 primary action and kept to two sentences with no filler. The parenthetical field/source enumeration is dense and partly duplicates the output schema, so it is informative but not maximally economical.

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 read-only five-parameter tool with an output schema, the description covers ordering, mode switching, coalescing and retention. Remaining gaps are the meaning of view=full versus summary and how workspaceId narrows results, though the output schema lowers the burden on return-value explanation.

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

Parameters3/5

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

With schema description coverage at 20%, the description must carry the load; it does explain versionId (read one version as a board summary) and hints at limit via the 50-version retention cap. But the view enum (summary vs full) is never explained, and projectId/workspaceId scoping is left entirely to the schema.

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 (list saved versions of a carousel board), then explicitly covers the second mode: passing versionId reads one version as a board summary. The enumerated return fields and source enum values (baseline, editor, agent, api, generation, restore) make it unmistakably the version-history tool rather than the board getter or restorer.

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 a clear selection rule for its two modes: omit versionId to list, supply versionId to read a single version. It does not mention when to reach for a sibling such as carousels_board_version_restore or carousels_board_get, nor any exclusions, so it stops short of full alternative routing.

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