Skip to main content
Glama

Outil.io

Set video background

set_video_background
Destructive

Fond du montage (couleur ou dégradé color→color2) visible derrière les plans réduits, masqués ou en carte arrondie et à la place des bandes noires. Exige la version actuelle du montage ; renvoie la nouvelle version.

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": {
      "projectId": "<projectId>",
      "version": "<version>",
      "background": "<background>"
    },
    "name": "set_video_background"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionYes
projectIdYes
backgroundYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation profile is known. The description adds genuinely useful behavior beyond that: it requires the current version (optimistic concurrency) and returns the new version. It does not say what is lost when the background is replaced, nor that a null background removes it, which matters for a destructive tool.

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?

Two tight sentences with the visual effect front-loaded and the version/return contract second. No filler. Minor deduction because the description is in French while the tool name and schema are English, which adds a small parsing cost for an English-oriented agent.

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

Completeness3/5

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

For a destructive, three-parameter mutation with no output schema and zero schema description coverage, the description covers the visual purpose and the version contract but omits the null/removal semantics and the angle parameter. An agent could call it, but might not know how to clear a background or what angle does.

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?

Schema description coverage is 0%, so the description must carry parameter meaning. It explains that background is a color or a color→color2 gradient and that version must be current, but it never mentions the angle parameter, the hex format, or that background may be null to clear the background. projectId is entirely unaddressed.

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 names a specific verb+resource (set the video background) and details what the background is: a solid color or a color→color2 gradient rendered behind reduced, masked, or rounded-card shots and in place of black bars. That is far more specific than the title. It does not, however, distinguish this tool from the sibling create_video_background, so an agent cannot tell the two apart from the text alone.

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?

Usage is implied by the rendering context (behind reduced/masked shots, replacing black bars), and one prerequisite is stated explicitly: the current version of the edit is required. There is no explicit when-to-use vs. when-not-to-use guidance and no mention of the sibling create_video_background, leaving the agent to infer the choice.

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.