Alto

Finish an upload and send it

complete_upload

Join the parts of an upload started with create_upload, create the video, and make one tracked link per recipient. Returns the video, its share link and each recipient's link.

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>",
      "parts": "<parts>",
      "title": "<title>"
    },
    "name": "complete_upload"
  }
}

Input Schema

Name	Required	Description
`slug`	No	The readable part of the link, optional.
`parts`	Yes	Every part's { part, etag }, from the PUTs.
`title`	Yes	What the prospect sees, e.g. "Fleet QA for Pruitt Logistics".
`duration`	No	Length in seconds. Needed unless Alto can measure the file.
`uploadId`	Yes
`recipients`	No	Who to send it to: one tracked link each. Strings like "Michelle Barba <michelle@pruitt.example>", or objects { name, email, company, title, note }.
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 9, 2026

changedInput schema / properties / recipients / description

Previous value: -"Who to send it to: one tracked link each. Strings like \"Michelle Barba <michelle@acme.example>\", or objects { name, email, company, title, note }."New value: +"Who to send it to: one tracked link each. Strings like \"Michelle Barba <michelle@pruitt.example>\", or objects { name, email, company, title, note }."

changedInput schema / properties / title / description

Previous value: -"What the prospect sees, e.g. \"Fleet QA for Acme Logistics\"."New value: +"What the prospect sees, e.g. \"Fleet QA for Pruitt Logistics\"."

Changed1 schema field changedOct 9, 2026

changedInput schema / properties / recipients / description

Previous value: -"Who to send it to: one tracked link each. Strings like \"Dana Whitfield <dana@acme.example>\", or objects { name, email, company, title, note }."New value: +"Who to send it to: one tracked link each. Strings like \"Michelle Barba <michelle@acme.example>\", or objects { name, email, company, title, note }."

First observedOct 1, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare it is a non-readonly, non-idempotent, non-destructive write with no open-world access. The description goes beyond them by disclosing the side effects (video creation plus one link per recipient) and the return payload (video, share link, per-recipient links), which matters since there is no output schema. It omits auth requirements or failure/retry behavior for a multi-part join.

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?

A single tight sentence: the action and its prerequisite come first, followed by the return values. No filler, no repetition of the title.

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?

With no output schema, the description compensates by summarizing the return shape, and it covers the cross-tool workflow dependency. It leaves some operational detail unstated (what happens to an expired/incomplete upload, partial failure semantics), but the essential picture for correct invocation is present.

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 coverage is 71%, so the schema documents most parameters (slug, parts, title, duration, recipients) on its own. The description only adds light framing, notably that recipients produce 'one tracked link each' and that parts come from an in-progress upload. That is marginal added meaning over the schema, fitting the baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States specific verbs and resources: joining upload parts, creating the video, and generating one tracked link per recipient. It explicitly ties itself to the sibling create_upload as the finishing step, so an agent can distinguish it from create_upload, upload_video, and create_link without opening schemas.

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?

Clearly establishes the prerequisite chain ('an upload started with create_upload'), which tells the agent when this tool applies. It does not name an alternative or state a when-not condition (e.g., versus upload_video or create_link), so it falls short of a full routing guideline.

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

All Alto tools Inspect

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

Need Help?