Skip to main content
Glama

Queue a full 5–15 minute narrated MP4 documentary

create_documentary_film

Submit a full 1080p 16:9 narrated faceless documentary render (5 min = 25 credits, 10 min = 50 credits, 15 min = 75 credits). Returns film_id in queued state; poll get_documentary_film until completed.

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": {
      "topic": "<topic>",
      "minutes": "<minutes>"
    },
    "name": "create_documentary_film"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoOptional angle or focus notes.
topicYesDocumentary topic (3–140 chars).
voiceNoNarrator voice: "olivia" (female) or "owen" (male).olivia
minutesYesTarget film length in minutes: 5 (25 credits), 10 (50 credits), or 15 (75 credits).
idempotency_keyNoOptional idempotency key so retries return the same film job.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations cover the safety profile (not read-only, open-world, non-destructive, not idempotent), and the description adds genuinely new behavior: the job is asynchronous and returns a film_id in queued state rather than the finished film, and it charges credits on a per-length schedule (25/50/75). It stops short of describing failure or refund behavior, which matters for a credit-charging render job.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero waste: the capability and cost schedule come first, then the return state and required follow-up call. Nothing could be removed without losing information the agent needs.

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

Completeness4/5

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

For a five-parameter async creation tool with no output schema, the description supplies the essentials: what is produced, what is returned, and how to get the result. It leaves out what happens when the render fails or credits run out, which is the main remaining gap for a paid, non-idempotent job.

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% and every parameter already carries a description, enum, or const, so the schema does the heavy lifting. The description only restates the minutes-to-credits mapping already present in the schema and adds no meaning for topic, voice, notes, or idempotency_key. 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?

States a specific verb and artifact: 'Submit a full 1080p 16:9 narrated faceless documentary render,' with format, resolution, and duration range. It is clearly distinguishable from the read/poll sibling get_documentary_film and from create_storyboard_preview, which the name implies is a cheaper preview step.

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?

The description supplies the post-call workflow explicitly: 'poll get_documentary_film until completed,' which tells the agent this tool is only the submission half of an async pair. It does not explicitly say when to prefer create_storyboard_preview or what to do on insufficient credits, so it falls short of full when/when-not guidance.

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.