Skip to main content
Glama

Outil.io

Update video text

update_video_text
Destructive

Remplacer le texte animé portant cet id (texte, temps, style, position). 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>",
      "text": "<text>"
    },
    "name": "update_video_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
versionYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/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 value beyond that by disclosing the optimistic-concurrency requirement (current project version) and the return value (the new version). It does not say whether the supplied text object fully replaces the element or merges with existing fields, which matters for a destructive nested-object update.

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 compact sentences, with the action and its target front-loaded and the precondition and return value following. Every clause carries information; the only friction is the parenthetical field list, which is terse enough to be slightly ambiguous ('temps' for the start/end pair).

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 over a fifteen-field nested object with no output schema and zero schema descriptions, the definition covers the essentials (targeting by id, required current version, returns new version). It is still thin on merge-versus-replace semantics, permission requirements, and error behavior, which an agent would need before invoking it confidently.

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 description coverage is 0% across a nested object with roughly fifteen fields, so the description must carry the burden and only partially does: the parenthetical '(texte, temps, style, position)' maps the categories of editable properties (text, start/end, font/size/color/preset/animation, x/y) onto the schema. It adds targeting semantics ('portant cet id') and the version parameter's role, but says nothing about units, defaults, or which fields are optional versus required.

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 opens with a specific verb+resource pair ('Remplacer le texte animé portant cet id') and enumerates the editable dimensions (texte, temps, style, position), so the agent knows this mutates an existing text element rather than creating one. It does not name add_video_text or remove_video_text explicitly, so the differentiation from siblings is implied by 'Remplacer ... portant cet id' rather than stated.

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 'Exige la version actuelle du montage' is a genuine precondition that tells the agent it must fetch the current project version first, which is real when-to-use guidance. However, there is no statement about when to use this versus add_video_text or remove_video_text, and no exclusion or failure condition beyond the version requirement.

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.