Skip to main content
Glama

Outil.io

Propose video edit

propose_video_edit
Read-only

Demander une proposition à la connexion IA du projet. Renvoie un document, sans le sauvegarder. Le fournisseur reçoit la timeline et les textes, pas les images ni le son.

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>",
      "instruction": "<instruction>"
    },
    "name": "propose_video_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionYes
projectIdYes
instructionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, yet the description adds real value beyond them: it discloses that data leaves the system to an external provider and precisely what is sent (timeline and texts, not images or audio). It also confirms no persistence. Gaps remain on latency, cost and failure modes for a remote AI call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, no filler, with the core action stated first and the data-sharing caveat last. Every sentence carries distinct information.

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?

Covering the external-data disclosure is important for a tool that ships the timeline off-site, but with no output schema the vague "Renvoie un document" leaves the return format undefined, and none of the three parameters are explained. Adequate but with clear gaps for a multi-parameter AI invocation.

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% across three required parameters, and the description mentions none of them. The meaning of "version" (document revision? optimistic concurrency token?) is left entirely ambiguous, as is the scope of "instruction" beyond its length bounds.

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 specific action and resource: request a proposal from the project's AI connection and return a document without persisting it. That distinguishes it from siblings like apply_video_edits or replace_video_document, though it never names an alternative explicitly.

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?

"Renvoie un document, sans le sauvegarder" implicitly tells the agent this produces an unsaved draft, so a separate apply/save step is needed. There is no explicit when-to-use condition, no prerequisites, and no named alternative for applying the proposal.

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.