WowReveal

Create a compilation (async)

create_compilation

Combine 2–30 finished projects (status complete) into one numbered long video — e.g. "Top 10 golden buzzers" (3+ min is a long-format video; whether Facebook runs ads in it is Meta's call). Costs 8 credits. Returns the project id immediately — then wait_for_project.

Input Schema

Name	Required	Description
`music`	No	"none" (default) or a Brand Kit music id (list_brand_assets).
`title`	Yes	Compilation title (also shown on the intro card).
`format`	No	vertical 9:16 (default) or horizontal 16:9.
`language`	No	Language of cards (default: the account's preference or en).
`numbering`	No	Number badges: countdown (#10 → #1, default), countup, none.
`intro_card`	No	Title card at the start (default true).
`outro_text`	No	Closing text.
`project_ids`	Yes	Finished project ids, in playback order.
`idempotency_key`	No	Optional unique key (e.g. a uuid) — repeating the same call with the same key within 24 h returns the first result instead of charging again.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

changedInput schema / properties / language / enum

Previous value: -[
-  "en",
-  "es",
-  "pt",
-  "fr",
-  "de",
-  "it",
-  "ru",
-  "hi",
-  "ar"
-]New value: +[
+  "en",
+  "es",
+  "pt",
+  "fr",
+  "de",
+  "it",
+  "ru",
+  "hi",
+  "ar",
+  "bn",
+  "ur",
+  "id",
+  "fil",
+  "vi",
+  "tr",
+  "ta",
+  "te",
+  "th",
+  "ms",
+  "ja",
+  "ko",
+  "zh",
+  "pl",
+  "uk",
+  "mr",
+  "pa",
+  "sw"
+]

Changed1 schema field changedOct 19, 2026

changedInput schema / properties / music / description

Previous value: -"\"none\" (default) or a Brand Kit music asset id."New value: +"\"none\" (default) or a Brand Kit music id (list_brand_assets)."

First observedOct 10, 2026

TDQS

A4.4/5.0

Behavior5/5

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

With annotations already covering safety hints, the description adds meaningful behavior: it costs 8 credits, returns a project id immediately, and requires following up with wait_for_project. It also discloses the prerequisite that source projects must be finished and the valid 2–30 project range.

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 key purpose, cost, and async behavior are front-loaded and easy to scan. The parenthetical about Facebook ads is slightly tangential, keeping it from being maximally concise.

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 async mutation with no output schema, the description provides the critical workflow details: what it creates, the credit cost, the immediate return value, and the required follow-up call. All parameter details are also fully covered by the schema.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all parameters in detail. The description adds only a little extra meaning, notably the status-complete requirement for source projects, so the baseline 3 is appropriate.

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 states a specific verb and resource: combine 2–30 finished projects into one numbered long video. It also distinguishes the output as a long-format compilation, which helps separate it from sibling tools like create_short.

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?

It clearly frames when to use the tool: to combine finished projects with status complete into a compilation. It also tells the agent what to do next by naming wait_for_project, though it does not explicitly compare this tool against alternatives.

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

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