Mondovo

Animate a carousel

animate_carousel

Idempotent

SPENDS CREDITS. When any slide walks through, call preview_carousel_animation FIRST and show the owner the character and frames; this renders exactly those. Start the animated carousel the owner approved: send the same slides, expected_credit_cost = the quoted credits, and a stable idempotency_key (a retry with the same key never charges twice). When any slide is "pass_through" and the carousel has no character yet, pass character — a saved_character_id from the plan's saved_characters (the brand's recurring characters; offer them first), or a description ("Rosie, a cheerful baker in a yellow apron"), a reference_url photo of the person, mascot or product, or both; it is drawn once, reused for every slide, and saved to the brand's characters for next time. Each moving slide renders in about a minute and is billed on its own: a slide that fails is refunded in full. Poll get_carousel_animation for the clips. To post: attach_visual_to_post with the carousel job_id attaches the clips in place of their slides once they are ready (Instagram only takes video slides in a carousel).

Input Schema

Name	Required	Description
`job_id`	Yes	The finished carousel job id
`slides`	Yes	The same per-slide motions you quoted
`character`	No	Needed once, when a slide is pass_through and the carousel has no character yet
`user_goal`	No	Optional: the user's goal behind this call, in one short sentence of plain words (e.g. "add a page so customers can book tables"). No names, emails or other personal details.
`idempotency_key`	Yes	Stable per approval; a retry with the same key is free
`expected_credit_cost`	Yes	The `credits` plan_carousel_animation returned

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

addedInput schema / properties / user_goal

Added value: +{
+  "description": "Optional: the user's goal behind this call, in one short sentence of plain words (e.g. \"add a page so customers can book tables\"). No names, emails or other personal details.",
+  "type": "string"
+}

First observedOct 19, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations cover idempotency and non-destructiveness, but the description adds the material economics and behavior: credits are spent, each slide is billed individually at ~1 minute, failed slides are refunded in full, and a repeated idempotency_key never double-charges. It also explains that a character is drawn once, reused per slide, and persisted to the brand's characters — none of which is in the annotations.

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 highest-stakes fact ('SPENDS CREDITS') and organized as approval → character → cost/timing → polling → posting. It is a single dense paragraph, though, and the character paragraph could be split for faster scanning.

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 credit-spending, nested-parameter mutation with no output schema, the description supplies the full lifecycle: prerequisite preview, approval contract, character fallback logic, billing/refund behavior, polling tool, and the publish handoff. Nothing an agent needs to call this safely is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds cross-call meaning the schema cannot: `slides` must match the quoted motions, `expected_credit_cost` must equal the quoted `credits`, and `idempotency_key` must be stable per approval. The `character` sub-fields are also tied to a source (`saved_characters` in the plan answer) that the schema only gestures at.

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 ('Start the animated carousel the owner approved') and immediately distinguishes itself from preview_carousel_animation, which must run first, and from get_carousel_animation, which polls results. An agent can route between these siblings from the description alone.

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 sequencing ('call preview_carousel_animation FIRST'), an approval precondition, an explicit follow-up ('Poll get_carousel_animation for the clips'), and a downstream route ('To post: attach_visual_to_post with the carousel job_id'). When-to-use and what-comes-next are both stated, not implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Mondovo tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?