Skip to main content
Glama

generate_carousel_slides

Draw the carousel's slide images in a style — at most 5 slides per call, in parallel (about 30-60 seconds). Uses one image credit per slide; a slide that fails is not charged.

Style: on the first call pass exactly one of theme_key (from list_carousel_themes) or custom_style (the user's own description of the look). Later calls reuse it, so omit both. Passing a different style restyles the deck: every slide then needs redrawing.

Which slides: by default the next slides that still need an image in the current style; or name them with slide_numbers (e.g. [3] to redo slide 3 after the user asked for changes). Keep calling until remaining is empty — follow next_step. If a call times out on your side, call get_carousel: slides that finished were saved.

ig_account_id is the Instagram account whose @handle and profile picture appear on the slides (needed when the workspace has more than one). slide_photo_urls maps a slide number to a public image link (a person, product or screenshot to put on that slide; key 0 = the cover photo, which otherwise defaults to the hook photo saved in reeldrop). Themes that need photos say so in list_carousel_themes. An empty string removes a slide's photo. logo puts the workspace's brand logo (set in reeldrop) on the cover or on every slide. Redrawing a slide keeps its previous image as an earlier version the user can go back to in reeldrop's Carousel Lab.

Images are drawn by reeldrop's image model provider (see reeldrop.io/privacy). Show the user the image_url of each finished slide.

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

Input Schema

NameRequiredDescriptionDefault
logoNonone
theme_keyNo
carousel_idYes
custom_styleNo
workspace_idYes
ig_account_idNo
slide_numbersNo
slide_photo_urlsNo

Output Schema

NameRequiredDescriptionDefault
failedYes
generatedYes
next_stepYes
remainingYes
theme_nameYes
carousel_idYes
image_credits_leftNo

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?

Goes well beyond the annotations: discloses credit cost per slide with failure not charged, the 30-60 second runtime, that a timed-out call still saves finished slides, that redrawing preserves the prior image as a restorable version, and that rendering uses an external provider (privacy link). The non-destructive claim in annotations is consistent with the 'previous version kept' behavior.

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 structured with labeled sections (Style / Which slides) and the key constraint front-loaded. Some sentences are long and a few points are restated (keep calling until remaining is empty / follow next_step), but nearly all content is load-bearing rather than 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, credit-consuming, multi-call generation tool, the definition covers the whole loop: first call, repeat calls, targeted redraws, termination condition, failure/timeout recovery, and what to show the user. Return-value details are appropriately delegated to the existing output schema.

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 must carry all meaning, and it does: it explains theme_key/custom_style exclusivity, slide_numbers semantics with an example, ig_account_id's purpose (handle/avatar) and when it is needed, slide_photo_urls' map structure including key 0 for cover and empty string to remove, and the logo enum. Only workspace_id/carousel_id are left implicit, and those are self-evident as required identifiers.

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+resource ('Draw the carousel's slide images') and immediately adds scope (max 5 per call, parallel, 30-60s). It is clearly distinguishable from siblings like update_carousel_slides or edit_carousel_slide, which mutate slide data rather than render images.

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?

Explicit routing rules: pass exactly one of theme_key or custom_style on the first call and omit on later calls, use slide_numbers to redo specific slides, keep calling until remaining is empty, follow next_step, and call get_carousel if the call times out. It also states the consequence of changing style (full redraw), which is a real usage trap.

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