Skip to main content
Glama

Outil.io

Cancel video upload

cancel_video_upload
Destructive

Supprimer les morceaux d’un import incomplet appartenant au projet. Ne supprime pas les médias déjà importés.

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

Input Schema

NameRequiredDescriptionDefault
uploadIdYes

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 safety profile is known. The description adds genuinely useful scope detail beyond that: only the chunks of an incomplete import are removed, and already-imported media is preserved — which is exactly the reassurance an agent needs before invoking a destructive tool. It still does not say what happens to the upload record itself or whether the operation is retryable.

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?

Two short sentences, zero filler, with the destructive scope stated first and the exclusion second. Nothing could be removed without losing meaning.

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

Completeness4/5

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

For a one-parameter destructive cleanup tool with no output schema, the definition covers the essential risk question (imported media is safe) and the target (incomplete import chunks). The remaining gap is the uploadId's provenance and the error behavior on a completed upload, which is minor but non-trivial for a destructive call.

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% and there is a single required parameter, uploadId, which the description never mentions or explains. It implies the id identifies 'un import incomplet', but does not state the expected source (e.g. the id returned by start_video_upload) or the behavior when the upload is already complete. With no schema coverage, the description should compensate and does not.

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 verb and resource ('Supprimer les morceaux d'un import incomplet') scoped to a project, which distinguishes it from the sibling upload-lifecycle tools (start_video_upload, complete_video_upload). It does not name those siblings explicitly, and the description is in French while the name/title are English, adding a small interpretation step for an English-speaking agent.

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 only implied: the phrase 'import incomplet' signals this applies to abandoned/partial uploads, and the second sentence carves out a when-not ('Ne supprime pas les médias déjà importés'). There is no explicit instruction on when to prefer this over complete_video_upload, nor any prerequisite about the upload's state.

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.