Skip to main content
Glama

Outil.io

Set video project settings

set_video_project_settings
Destructive

Modifier le nom, le format ou la résolution du montage sans réécrire ses pistes. 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>"
    },
    "name": "set_video_project_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
ratioNo
versionYes
projectIdYes
resolutionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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; the description adds genuinely useful concurrency semantics ('Exige la version actuelle du montage ; renvoie la nouvelle version') and clarifies that tracks are not rewritten. However, it never explains the actual destructive consequence of destructiveHint=true — e.g. whether changing ratio/resolution reframes or crops existing clips — nor whether omitted fields are left untouched.

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 dense sentences with the mutating scope front-loaded and the version contract second; nothing is padded. It is written in French while the title, siblings, and annotations are English, which is a minor structural inconsistency across the toolset.

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 mutation with five parameters at 0% schema coverage and no output schema, the description covers the field set and the version contract but omits what the destructive behavior means in practice and what happens to unspecified fields. That is a meaningful gap for settings that could alter existing edits.

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 coverage is 0%, so the description carries the burden, and it does map to name, ratio ('format'), resolution, and the required version/optimistic-concurrency contract. It adds nothing about the enum semantics of ratio (16:9/9:16/1:1) or resolution ("720"/"1080", whose unit is ambiguous), and projectId is never mentioned.

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 ('Modifier') and resource ('le montage') plus the exact fields it touches: nom, format, résolution. That distinguishes it from sibling track/clip-level setters such as set_video_transform or set_video_clip_speed. It does not explicitly name a sibling, so it falls short of a 5.

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 clause 'sans réécrire ses pistes' implicitly signals this is the lightweight project-level alternative to operations that rewrite media, but no explicit when-to-use, when-not-to-use, or named alternative is given. Usage is inferable rather than stated.

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.