Export a video clip as an animated GIF up to 30 seconds long, using an optimized palette for efficient file size.
Export a GIF excerpt with an optimised palette (30 seconds max).
| Name | Required | Description | Default |
|---|---|---|---|
| fps | No | ||
| input | Yes | ||
| start | No | ||
| width | No | ||
| duration | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description must carry the behavioral burden. It mentions the 30-second max duration and optimized palette, but fails to disclose side effects, output location, post-processing behavior, or any potential blocking/long-running nature. The description gives minimal behavioral context for a file-export operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence that conveys the core purpose and a key constraint without waste. It is appropriately concise for the tool's simple purpose, though it sacrifices important details.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with five parameters, no annotations, and no output schema, the description leaves critical gaps: what the 'input' should be, where the output goes, how to retrieve it, and any side effects. The sibling context suggests a media pipeline, but the description alone is insufficient for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate for the five undocumented parameters. It only hints at '30 seconds max' (matching the duration limit) and 'excerpt' (implying start/duration), but does not explain fps, width, or the input string format. This adds marginal value over the raw schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool exports a GIF excerpt with an optimized palette, using a specific verb and resource. It does not explicitly differentiate from siblings like media_extract_frames or clip_format_convert, but the purpose is unambiguous enough for an agent to identify it.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives such as clip_format_convert or render_start. There is no mention of prerequisites, input media requirements, or scenarios where a different export format would be preferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.