Skip to main content
Glama

list_carousels

Read-onlyIdempotent

The workspace's carousels, newest activity first — drafts, ones being drawn, and finished ones, whether made here or in reeldrop's Carousel Lab.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
workspace_idYes

Output Schema

NameRequiredDescriptionDefault
carouselsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive, closed-world behavior, so the description only needs to add context. It does: it discloses the sort order (newest activity first) and that results span all statuses and both creation sources, which an agent cannot infer from annotations or schema. It does not mention pagination behavior, which is the main remaining gap.

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?

A single front-loaded sentence that leads with the resource and then qualifies ordering and coverage. No filler, though the 'ones being drawn' phrasing is slightly more colorful than needed for an agent-facing definition.

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?

An output schema exists, so return shape needn't be explained, and the description covers scope and ordering well. However, for a list tool with a limit parameter and no schema descriptions, the absence of any pagination or default-page-size guidance leaves a real operational gap.

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% — neither workspace_id nor limit has any documented meaning. The description only implies workspace scoping ('The workspace's carousels') and says nothing about limit, its default of 20, or maximum page size, so it fails to compensate for the coverage gap.

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+resource (list the workspace's carousels) and adds scope details: newest activity first, all lifecycle states (drafts, in-progress, finished), and both locally created and Carousel Lab items. It doesn't explicitly distinguish itself from get_carousel or list_carousel_themes, but 'list' vs. 'get' is reasonably readable from the name.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative (e.g., 'use get_carousel for a single carousel'). The workspace scoping is implied, but an agent gets no routing signal beyond the tool name.

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