Skip to main content
Glama

Outil.io

Create video project

create_video_project

Créer un montage vide dans le projet courant. Ajouter ensuite les médias avec les outils clip/piste. Ne crée pas de nouveau workspace Outil.

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": {
      "name": "<name>"
    },
    "name": "create_video_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
ratioNo9:16
resolutionNo720

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 readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the write-but-non-destructive profile is known. The description adds useful scope context (empty sequence created inside the current project, no workspace creation) but says nothing about permissions, defaults applied, or what is returned after creation.

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, purpose first, then next step, then exclusion – well front-loaded with no filler. However, the description is in French while titles/annotations are English, a minor inconsistency for downstream routing.

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 creation tool with three undocumented parameters and no output schema, the description should at least say what identifier or object comes back so the agent can chain clip/track calls. It covers intent and scope but leaves parameters and return value entirely to inference.

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 coverage is 0% – none of name, ratio or resolution is documented in the schema. The description compensates for none of it: it never mentions that a name is required, nor how ratio/resolution defaults (9:16, 720) affect the created project.

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?

States a concrete verb and resource ('Créer un montage vide') and scopes it to 'le projet courant', which separates it from create_project/create_workspace siblings. It does not name sibling tools, so differentiation is implied rather than explicit.

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?

Gives the follow-up path ('Ajouter ensuite les médias avec les outils clip/piste') and an explicit exclusion ('Ne crée pas de nouveau workspace'), which tells the agent when not to use it. It lacks guidance on when to use create_project or duplicate_video_project instead.

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.