Skip to main content
Glama
Sign In

Vidova

by ai.vidova
OverviewDiscussionsAdmin

Complete a file upload

complete_asset_upload
Idempotent

Complete an upload after the upload commands succeed. Use the Asset ID returned by begin_asset_upload. A video may still be processing: the result then says NOT PLACEABLE YET and ends with a NEXT line; call wait_for_asset with the Asset ID, which answers once the asset is placeable.

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": {
      "assetId": "<assetId>",
      "projectId": "<projectId>"
    },
    "name": "complete_asset_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetIdYes
projectIdYesThe project this call runs on without changing the open project. null (or leaving it out) uses the open project. wait_for_jobs takes the projectId of the calls that started the jobs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations only declare mutation/idempotency/safety hints; the description goes further by disclosing the async processing state and the literal result contract ('says NOT PLACEABLE YET and ends with a NEXT line'). With no output schema, that return-shape detail is real added value. It stops short of describing what a successful, placeable completion returns.

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?

Three short sentences, front-loaded with the action and precondition, then the edge case and its remedy. Every sentence carries distinct information; the quoted result tokens are precise rather than padding.

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

Completeness5/5

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

For a two-parameter mutation tool with no output schema, the description covers the action, the ID source, the failure-mode branch, and the follow-up tool. The remaining unknowns (idempotency, safety) are already supplied by annotations, so an agent has what it needs to call correctly.

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 50%: projectId is well documented in the schema, but assetId carries no description there. The description compensates by explaining assetId's provenance ('returned by begin_asset_upload'), which is the one piece of semantics an agent couldn't infer. projectId semantics are left entirely to the schema.

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 a specific verb and resource ('Complete an upload') and anchors it in a lifecycle by naming the predecessor tool ('after the upload commands succeed', 'the Asset ID returned by begin_asset_upload'). This clearly separates it from begin_asset_upload and wait_for_asset in the sibling list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit precondition for calling (after upload commands succeed) and an explicit branch condition that routes to the alternative ('A video may still be processing ... call wait_for_asset with the Asset ID'). The when-to-use and the when-to-switch-tools case are both spelled out.

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

All Vidova 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