Skip to main content
Glama

Prepare a short film from a sentence

create_film

Prepares a short film from one sentence: 3 to 6 shots, about 15 to 30 seconds, the same character throughout, with sound, music and editing. Returns the link to Cirrela's Film page with the idea filled in, where the person gets story ideas and a storyboard, sees the cost in credits, and makes the film with one tap after signing in. Nothing is rendered or spent in the chat, and no sign-in is needed to get the link. Fits "make a video of…", "fais une vidéo de…", "haz un vídeo de…", "faça um vídeo de…" when the person wants a little story rather than one clip.

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": {
      "idea": "<idea>"
    },
    "name": "create_film"
  }
}

Input Schema

NameRequiredDescriptionDefault
ideaYesThe film in a sentence or two: who, where, what happens.
languageNoOptional: the page's language, usually the one the person writes in. Default en.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare non-destructive but non-read-only behavior; the description goes well beyond them by disclosing that nothing is rendered or spent in chat, that the return value is a link to a Film page with cost in credits shown, and that sign-in is only needed later to actually produce the film. That is exactly the cost/auth/side-effect context an agent needs before calling.

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 core capability and scope are front-loaded, followed by return behavior and then routing cues; every sentence carries information. The multilingual phrase list is slightly bulky but serves a real routing purpose, so the length is justified.

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?

With no output schema, the description compensates by explaining the return is a link to a pre-filled Film page and what the person does there (story ideas, storyboard, credit cost, one-tap render). Nothing needed to call it correctly or set expectations afterward 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 both parameters are already documented; the description nonetheless frames 'idea' as one sentence of who/where/what happens and clarifies that 'language' should usually match the person's writing language. That adds useful interpretive meaning beyond the raw schema, though not enough to warrant a top score.

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 names a specific verb and resource ('Prepares a short film') and immediately pins down scope: 3 to 6 shots, 15-30 seconds, one character throughout, with sound, music and editing. It also distinguishes itself from the single-clip sibling by stating it is for when 'the person wants a little story rather than one clip.'

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?

It gives concrete trigger phrasings across four languages ('make a video of…', 'fais une vidéo de…', etc.) and an explicit exclusion criterion versus the one-clip alternative. The agent knows both when to select it and when not to.

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.

Resources