Skip to main content
Glama

Outil.io

Create video background

create_video_background

Créer un plan de fond uni ou dégradé animé (écran de titre, transition, fin) à couvrir de textes animés.

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_video_background"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
angleNo
colorNo#111827
ratioNo9:16
color2No
secondsNo
animatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the agent knows this is a non-destructive, closed-world creation. The description adds the useful framing that the output is a bare background meant to be overlaid with text, but it omits what is actually produced (clip, layer, asset), where it is registered, and the default behavior (3s, 9:16, animated) applied when nothing is passed.

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?

A single front-loaded sentence with the verb first and the intended use cases in parentheses; nothing is redundant. It is arguably too short for a 7-parameter tool, but the wording itself is efficient.

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

Completeness2/5

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

For a tool with 7 undocumented parameters, no output schema and modest annotations, the description is far too thin: it explains neither the parameter semantics nor the returned artifact or where it lands. An agent could not confidently call it with correct values without reverse-engineering the raw schema.

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?

With 7 parameters at 0% schema description coverage, the description carries the full burden and largely fails: it never mentions name, angle, color/color2, ratio, seconds or animated. Only 'uni ou dégradé' faintly hints at the two-color gradient and 'animé' hints at the animated flag, leaving angle, ratio, duration and naming entirely unexplained.

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 verb+resource are specific: creating a solid or animated-gradient background shot for use as a title screen, transition, or end card, intended to be covered with animated text. This separates it reasonably from set_video_background (configure an existing one) and from add_video_text/add_video_layer. It is slightly weakened by being written in French while the tool name, title and annotations are English.

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?

The parenthetical '(écran de titre, transition, fin)' implies the scenarios where this tool is appropriate, so usage is inferable. However, there is no explicit statement of when to use this versus set_video_background, nor any prerequisite such as an existing video project or the need to add text afterward.

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.