Kuro

Create a carousel

create_carousel

Render 2–20 pictures, in order, into one carousel: an image set in the library, one picture per page, each with at most one line of text and one inset (a real screenshot in a phone frame). Every source is a ready image generation or an image upload. Text sits at top, middle or bottom inside the canvas's reading zone, in one style for the whole set; a line too long for its band shrinks until it fits, down to 24px, so keep lines short enough to read on a phone. Rendering costs no credits and returns immediately with the set's generation id; get_generation waits until it is ready, then get_download_url on it returns one ordered ZIP.

Input Schema

TableJSON Schema

Name	Required	Description
`pages`	Yes	In page order. source is { type: "generation", generation_id } or { type: "upload", upload_id }. text is null or { content, position: "top" \| "middle" \| "bottom" }. inset is null or { source, frame: "phone" \| "none" }. focus { x, y } anchors the crop, 0.5/0.5 by default.
`style`	No	How every line is set: { align, font_id, font_weight, font_size, color, outline, box }. Omitted, the photo-slideshow look: tiktok-sans at 600, 64px, white with outline, no box. box puts a solid band behind each line.
`title`	No	The set's name in the library; pages are named after it.
`canvas`	Yes	The page shape: 9:16 for a TikTok photo post, 4:5 for an Instagram feed carousel.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`message`	Yes
`generation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 21, 2026

addedOutput schema / properties / generation / properties / ready_in_seconds
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```

changedOutput schema / properties / generation / required

Previous value: -[
-  "generation_id",
-  "kind",
-  "status",
-  "model",
-  "prompt",
-  "aspect_ratio",
-  "refined_from",
-  "caption_style",
-  "output_url",
-  "credits_cost",
-  "error",
-  "vendor_phase",
-  "stalled",
-  "created_at",
-  "app_url"
-]New value: +[
+  "generation_id",
+  "kind",
+  "status",
+  "model",
+  "prompt",
+  "aspect_ratio",
+  "refined_from",
+  "caption_style",
+  "output_url",
+  "credits_cost",
+  "error",
+  "vendor_phase",
+  "stalled",
+  "ready_in_seconds",
+  "created_at",
+  "app_url"
+]

First observedOct 15, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Adds context beyond annotations: rendering costs no credits, returns immediately with a generation id, and is asynchronous, which matters given idempotentHint=false and readOnlyHint=false. It also discloses the text-shrink behavior and the 24px floor, i.e. what happens when input exceeds the band, which is genuine behavioral detail.

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?

Purpose and the page-count constraint are front-loaded, and every clause carries information (limits, credit cost, async flow, shrink guard). It is a single dense block of run-on sentences, though, which slightly hurts scannability.

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 tool with a fully described nested schema and an output schema, the description covers what structured fields cannot: the async render pipeline, the follow-up calls, and the credit cost. Nothing needed to invoke it correctly or to retrieve its output 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 meaning the schema cannot convey: one style applies to the whole set rather than per page, text sits in top/middle/bottom 'reading zones', and an inset is a real screenshot in a phone frame. Minor gap: 'canvas' and 'focus' semantics are left to the schema.

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 ('Render 2–20 pictures, in order, into one carousel: an image set in the library, one picture per page'), which distinguishes it from generate_image or edit_image siblings. The output artifact (a library image set with ordered pages) is concrete enough that an agent can tell it apart without reading the schema.

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

Usage Guidelines4/5

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

Explicitly constrains sources to a ready image generation or an upload, and routes the agent through the follow-up flow (get_generation, then get_download_url). It lacks an explicit 'use X instead when...' exclusion against siblings like generate_scene_images, which keeps it below a 5.

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

All Kuro 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?