Skip to main content
Glama

Outil.io

Start video upload

start_video_upload

Ouvrir un import multipart privé au projet. Retourne id et chunkSize pour upload_video_chunk, puis complete_video_upload.

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>",
      "mime": "<mime>",
      "size": "<size>"
    },
    "name": "start_video_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
mimeYes
nameYes
sizeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 mutation and safety profile is covered structurally. The description adds that the import is 'privé' (private) and that it yields an id and chunkSize for subsequent calls, which is useful beyond the annotations. It says nothing about auth/permission requirements, what happens to an abandoned upload, or whether the upload session expires.

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 short sentences with no filler, and the action is front-loaded before the follow-on tooling. The second sentence compresses return values and sequencing into one clause, which is efficient but slightly dense.

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

Completeness2/5

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

There is no output schema, and the description does cover the returned id and chunkSize, which is a genuine plus. However, for a three-parameter initiation tool with zero schema descriptions, it omits parameter meaning and limits (max size, accepted mime types), leaving an agent to guess at call correctness.

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 all three parameters (name, mime, size) are required, yet the description never mentions any of them. Constraints such as the 256 MB size ceiling and the mime enum are left entirely to the schema, so the description does not compensate for the coverage gap.

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 states a specific action and resource: opening a private multipart upload attached to the project. It also names the two follow-on tools (upload_video_chunk, complete_video_upload), which distinguishes this step from siblings in the same upload family. It stops short of contrasting with non-multipart alternatives such as upload_asset.

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?

The workflow ordering is explicit: this tool returns the id and chunkSize needed by upload_video_chunk, and complete_video_upload finishes the job. That tells an agent where this call sits in the sequence. There are no stated preconditions or exclusions (e.g., when to prefer a single-shot asset upload 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.