Skip to main content
Glama

create_carousel

Start an AI carousel: write the text of every slide from a topic, with Google Gemini (see reeldrop.io/privacy). No images yet, and no credits used.

slide_count is the total number of slides (1-10), cover and closing slide included. Slide 0 is the cover (its hook is the title); slides 1..N carry a hook and bullets_per_slide points (0 = one short paragraph). With include_cta the last slide is a follow/save/share sign-off. One slide makes a single-page infographic (no cover, no sign-off). tone is one of default, humorous, bold, inspirational, educational. custom_instructions steers the writing (audience, angle, must-mention points).

Show the user every slide's text and ask for changes before drawing anything — fix wording with update_carousel_slides. Then help them choose a style (list_carousel_themes) and call generate_carousel_slides.

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

Input Schema

NameRequiredDescriptionDefault
toneNodefault
topicYes
include_ctaNo
slide_countNo
workspace_idYes
include_coverNo
bullets_per_slideNo
custom_instructionsNo

Output Schema

NameRequiredDescriptionDefault
noteNo
topicYes
slidesYes
statusYes
theme_keyNo
created_atYes
theme_nameNo
updated_atYes
carousel_idYes
slides_needing_imagesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare the generic mutation profile (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false). The description adds behavior the agent could not otherwise know: an external Google Gemini call with a privacy reference, that no images are drawn yet, and that no credits are consumed — a materially important cost/side-effect disclosure.

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?

Well front-loaded: purpose first, then parameter semantics, then the workflow the agent must follow. It is on the dense side, with slight redundancy between 'No images yet' and 'before drawing anything', but no sentence is filler.

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 an 8-parameter, multi-step creation tool with an output schema, this covers what matters: what is produced, what is not yet produced, cost implications, parameter meaning, and the required human-in-the-loop handoff to sibling tools. Nothing an agent needs in order to call it correctly is missing.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden and largely does: it gives the slide_count range (1-10) and inclusive meaning, explains slide 0 as the cover and 1..N as hook+bullets, defines bullets_per_slide=0 as a single paragraph, lists the five allowed tone values that the schema does not enumerate, and describes include_cta and custom_instructions. Only workspace_id and include_cover are left implicit.

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?

Opens with a specific verb and resource: 'Start an AI carousel: write the text of every slide from a topic.' It immediately distinguishes this from generate_carousel_slides ('No images yet') and from update_carousel_slides (text revision), so an agent can route correctly without opening any schema.

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?

Gives an explicit sequence: show the user every slide's text and ask for changes, fix wording with update_carousel_slides, then choose a style via list_carousel_themes and call generate_carousel_slides. It names both the alternatives and the condition that selects each one, leaving nothing to inference.

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