Skip to main content
Glama

Film Leader Countdown Maker

create_film_leader_countdown
Read-onlyIdempotent

Prefill the Film Leader Countdown Maker: a classic film leader countdown with grain, scratches and flicker. Returns a link that opens the Tool with these options; the user presses Export there to download the video. All options are optional. Icons and images that need a file upload are not supported.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_film_leader_countdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
bgNoColor of the film leader background. Default: "#d3d3d3".
fpsNoExport frame rate. Default: "30".
inkNoColor of the numbers and rings. Default: "#1b1e1b".
resNoExport resolution. Default: "720".
vigNoDarkened vignette around the edges: 1 on, 0 off. Default: true.
sizeNoVideo size (aspect ratio) preset. Default: "16:9".
grainNoIntensity of the film grain effect. Default: "medium".
hairsNoIntensity of the film hairs effect. Default: "medium".
soundNoSound played at each count; "off" for silence. Default: "clip1".
startNoNumber the countdown starts from, counting down to 1. Default: 10.
jitterNoIntensity of the film jitter effect. Default: "medium".
flickerNoIntensity of the film flicker effect. Default: "medium".
vigsizeNoHow far the vignette reaches in from the edges. Default: 100.
intervalNoSeconds each number stays on screen. Default: 1.
vigalphaNoHow strong the vignette is. Default: 50.
vigcolorNoColor of the vignette. Default: "#141414".
scratchesNoIntensity of the film scratches effect. Default: "medium".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare this non-destructive, idempotent and read-only, so the description is not carrying the safety burden. It adds genuinely useful behavior beyond them: the call returns a link rather than a video, and rendering requires a separate user action. The upload limitation is also a real constraint an agent could otherwise trip over.

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?

Three short sentences, front-loaded with what gets built, followed by the return/export mechanic and the constraint. The aesthetic clause ('grain, scratches and flicker') slightly restates what the schema enums already reveal, but it earns its place by setting expectations for the result.

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 17-parameter, zero-required tool with full schema coverage and no output schema, the description supplies the pieces the schema cannot: there is no video returned, only a link, and the user completes the export. That covers what an agent needs to call it and correctly report the outcome to a user.

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% with defaults and enum ranges documented per parameter, so the schema already does the heavy lifting. The description only adds that every parameter is optional and that upload-based options do not apply, which is correct but minimal.

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 states a specific verb (prefill) and a specific resource (Film Leader Countdown Maker), plus the visual character of the output (grain, scratches, flicker) and the return type (a link). It is clearly distinct from the sibling animation tools, though it never explicitly contrasts itself with them.

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 gives clear operational context: all options are optional, the tool only pre-fills state, and the user must press Export in the opened tool to actually download the video. It also states a real exclusion (icons/images requiring file upload are unsupported). It stops short of naming when to choose this over the sibling animation makers, 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.