Skip to main content
Glama
Sign In

Valmera — AI Video Editor

by io.valmera
OverviewDiscussionsAdmin

Start uploading a local file

upload_start

Prepares a local-file upload for an explicit project and returns presigned storage URLs and the upload-completion contract. Supported kinds include main video, supplemental clip, music and image; clips may have a reference-only shorts role.

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": {
      "project_id": "<project_id>",
      "filename": "<filename>",
      "size_bytes": "<size_bytes>"
    },
    "name": "upload_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
roleNoOptional and valid only with kind='clip'. Makes the upload reference-only Shorts style input, not placeable media.
filenameYesName with extension, e.g. talk.mp4
duration_sNoOptional locally measured media duration in seconds, retained in the upload-completion contract.
project_idYesExplicit project identifier for this request. The connection's navigation pointer does not select the target.
size_bytesYesExact size of the local file

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / duration_s / description
      Previous value: -"Optional locally probed media duration in seconds; repeated in the returned upload_finish contract."New value: +"Optional locally measured media duration in seconds, retained in the upload-completion contract."
    • addedInput schema / properties / project_id / description
      Added value: +"Explicit project identifier for this request. The connection's navigation pointer does not select the target."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations declare the mutation profile (readOnly=false, destructive=false, idempotent=false), so the description needn't restate safety. It adds real context by disclosing the return contract — presigned storage URLs and an upload-completion contract — which matters because there is no output schema, and by explaining the reference-only shorts role, which is a non-obvious behavioral consequence. It does not mention URL expiry or what happens on a repeated call despite idempotentHint=false.

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 tight sentences: the action and its output come first, the kind/role qualifications second. Nothing is padded, though the phrase 'upload-completion contract' is jargon an agent must interpret without further explanation.

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 six-parameter, non-idempotent two-phase upload with no output schema, the description covers the inputs and the immediate return value but omits the follow-up step (presumably upload_finish) and any expiry or size constraints. An agent can start the upload but cannot tell from the description alone how to finish it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 83%, so the baseline is 3. The description goes beyond it by translating the 'kind' enum into domain terms ('main video, supplemental clip, music and image') and by stating that clips may carry a reference-only shorts role, which clarifies the interaction between the 'kind' and 'role' enums that the schema only hints at.

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 ('Prepares a local-file upload') scoped to 'an explicit project', and names what comes back (presigned storage URLs plus an upload-completion contract). It stops short of naming the sibling that finishes the job (upload_finish), so the two-phase flow must be inferred rather than read.

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 description implies usage by enumerating supported kinds (main video, supplemental clip, music, image) and the reference-only shorts role, which helps an agent decide whether this tool fits the asset at hand. It gives no explicit when-not guidance, no mention of prerequisites or limits, and no routing to alternatives such as add_stock_media, fetch_url, or attach.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Valmera — AI Video Editor toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources