Skip to main content
Glama

Compeller

by ai.compeller

create_compel

Create a Compeller generation job from primary audio media and optional reference media. Returns compel id, status, and links to track progress and retrieve renderings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
styleNoVisual style. Use one of the exact ids returned by list_styles (e.g. "Cinematic Realistic", "Anime / Manga"). Omit to use the account default.
titleYesTitle for the compel
aspect_ratioNoExplicit aspect ratio override (takes precedence over target_platform).
artist_contextNoAdditional creative context about the artist or song
target_platformNoTarget platform; sets the aspect ratio when aspect_ratio is omitted.
primary_media_idYesID of the uploaded audio media to use as the primary track

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed6 schema fields changed
    • changedInput schema / properties / aspect_ratio / description
      Previous value: -"Explicit aspect ratio override: 16:9, 9:16, or 1:1"New value: +"Explicit aspect ratio override (takes precedence over target_platform)."
    • addedInput schema / properties / aspect_ratio / enum
      Added value: +[
+  "16:9",
+  "9:16",
+  "1:1"
+]
    • changedInput schema / properties / style / description
      Previous value: -"Visual style: cinematic, performance, or abstract"New value: +"Visual style. Use one of the exact ids returned by list_styles (e.g. \"Cinematic Realistic\", \"Anime / Manga\"). Omit to use the account default."
    • addedInput schema / properties / style / enum
      Added value: +[
+  "Cinematic Realistic",
+  "Photo Realistic",
+  "Cyberpunk",
+  "Anime / Manga",
+  "Film Noir",
+  "Watercolor Painting",
+  "Oil Painting",
+  "3D Render / Pixar",
+  "Retro 80s Synthwave",
+  "Vintage Film Grain",
+  "Comic Book / Pop Art",
+  "Fantasy / Ethereal",
+  "Horror / Dark Gothic",
+  "Steampunk",
+  "Neon Glow",
+  "Minimalist / Abstract",
+  "Surrealist",
+  "Documentary",
+  "Vaporwave",
+  "Pencil Sketch",
+  "Noir Detective",
+  "Claymation / Stop Motion",
+  "Studio Ghibli",
+  "Baroque / Renaissance",
+  "Lo-Fi / Grainy VHS",
+  "Glitch Art / Digital",
+  "Psychedelic"
+]
    • changedInput schema / properties / target_platform / description
      Previous value: -"Target platform for aspect ratio: tiktok, reels, shorts, instagram, youtube"New value: +"Target platform; sets the aspect ratio when aspect_ratio is omitted."
    • addedInput schema / properties / target_platform / enum
      Added value: +[
+  "tiktok",
+  "reels",
+  "shorts",
+  "instagram",
+  "square",
+  "youtube",
+  "web"
+]
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the safety profile is clear. The description adds value by disclosing the return format (compel ID, status, tracking links), which is not in the annotations. However, the false claim about reference media slightly reduces trustworthiness.

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 description is concise, consisting of one sentence that covers the action, inputs, and outputs. However, the 'optional reference media' phrase is unnecessary and potentially misleading, so not every element earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description captures the core creation purpose and return information, which is important given the lack of an output schema. However, it omits the fact that style must be selected from list_styles and falsely claims reference media support, leaving the tool's full behavior only partially described.

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

Parameters2/5

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

All schema parameters have descriptions, so baseline is 3. However, the description introduces 'optional reference media' with no corresponding parameter, actively confusing parameter understanding. It adds no useful semantics for the actual parameters beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it creates a Compeller generation job from primary audio media, with a specific verb and resource. It distinguishes from sibling create_compel_from_music, but the mention of 'optional reference media' is not supported by the schema, slightly muddying the purpose.

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

Usage Guidelines3/5

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

It provides clear context that this is for creating a compel from uploaded audio, but does not mention alternatives or exclusion criteria. The unsupported 'optional reference media' reference could mislead an agent into thinking there is a parameter for it, harming usage guidance.

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

All Compeller toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation5/5

Every tool targets a distinct action or resource. Groups like compels, lighting cues, webhooks, and account are clearly separated, and even similar tools (create_compel vs create_compel_from_music) have well-defined differences in input source.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with underscores (e.g., cancel_compel, launch_lighting_cue, register_webhook). No mixing of conventions or ambiguous verb choices.

Tool Count2/5

With 30 tools, the server is above the 25+ threshold for 'too many'. While the scope includes multiple subdomains, the high number adds cognitive load and risks selection errors for an agent.

Completeness3/5

Core workflows are present (create, read, cancel, list, search, render), but missing update/delete for compels and media, and no way to modify render configuration beyond defaults.

Resources