Skip to main content
Glama

list_carousel_themes

Read-onlyIdempotent

The visual styles (themes) an AI carousel can be drawn in — the same gallery as reeldrop's Carousel Lab.

Show the user a few that fit their topic (name, description and a preview image) and let them choose; pass the chosen key to generate_carousel_slides as theme_key. Instead of a theme they can describe their own look, passed as custom_style. A theme with needs_cover_photo draws the creator from their cover photo, and slide_photos: "required" needs a photo for every content slide — check those before picking one for a user who has no photos to give.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_carousel_themes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
noteNo
themesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

The annotations already declare this is a read-only, idempotent, closed-world listing, so the safety profile is covered. The description adds genuine behavioral context beyond that: what fields a theme carries (name, description, preview image) and the meaning of two attributes (needs_cover_photo, slide_photos: "required") that act as preconditions for a later call. It stops short of saying how many themes return or anything about ordering/pagination, which keeps it from a 5.

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?

The purpose and the why-this-tool statement are front-loaded, and most sentences carry real information (the theme_key handoff, the custom_style alternative, the photo preconditions). It runs slightly long across three paragraph-like blocks, and the awkward line break mid-sentence in the first line hurts scanability a little.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read tool with an output schema and full annotations, the description covers everything an agent needs: what the tool returns, how to present it to a user, where the chosen value goes, and the alternative route. The presence of an output schema means return formatting need not be explained further.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description wisely spends its space on how the return values are consumed downstream instead.

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?

The description opens with a specific resource definition ('visual styles (themes) an AI carousel can be drawn in') and ties it to a concrete analog ('reeldrop's Carousel Lab'), making clear this is a catalog-listing tool rather than a generator. It is distinguishable from generate_carousel_slides, which it explicitly references as the consumer of the returned key.

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

Usage Guidelines5/5

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

It spells out the intended workflow: show the user a few themes that fit their topic, let them choose, then pass the chosen key to generate_carousel_slides as theme_key. It also names the alternative path (custom_style when the user wants their own look) and gives a selection guardrail (check needs_cover_photo and slide_photos before picking for a user with no photos).

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