Simpler.Asia

studio.finish_asset_upload

Finish an upload started with studio.begin_asset_upload once every part is PUT: the stored bytes are checked (the moov box is read wherever it sits), counted against the 20 GB quota, and added to the project's media. Returns {asset_id, media_type, probe}. Calling it again returns the same asset. Refuses: parts not yet sent (SIMPLER_STUDIO_UPLOAD_PARTS_MISSING lists them): PUT them, then finish again; bytes that are not the declared type (SIMPLER_STUDIO_UPLOAD_CONTENT_MISMATCH; the file is deleted): begin again with the real mime; a cancelled or expired upload (SIMPLER_STUDIO_UPLOAD_NOT_OPEN): begin again. Free.

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>",
      "upload_id": "<upload_id>"
    },
    "name": "studio.finish_asset_upload"
  }
}

Input Schema

Name	Required	Description	Default
`upload_id`	Yes	The upload (vup_...) studio.begin_asset_upload returned.
`project_id`	Yes	The studio project (vp_...) the upload belongs to.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only supply readOnlyHint=false, so the description carries the real behavioral load: it discloses validation steps (moov box read anywhere in the file), the 20 GB quota accounting, the side effect of adding to project media, deletion of the offending file on mismatch, and that the call is free. This is consistent with readOnlyHint=false (it is a state-changing finalize).

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?

Front-loads the preconditions and return shape, then packs the error taxonomy into one dense paragraph with zero filler. The error-cascade phrasing is a bit run-on, but every clause carries operational information.

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?

No output schema exists, and the description compensates by naming the return object ({asset_id, media_type, probe}). Combined with error codes and recovery paths, an agent has everything needed to call, retry, and interpret the result.

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 description coverage is 100% and both parameters already carry descriptions (upload_id vup_..., project_id vp_...), so the description adds nothing about parameter formats or constraints. The 'vup_...'/'vp_...' prefixes live in the schema, not the prose. Baseline 3 applies.

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 operation — finalize an upload started by studio.begin_asset_upload — and names the sibling that initiates it, so the agent can place it in the upload lifecycle without consulting other schemas. It also names the resource (project media) the bytes land in.

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?

Explicit precondition ('once every part is PUT') plus a full remediation table for each refusal: missing parts → PUT then finish again; content mismatch → begin again with the real mime; cancelled/expired → begin again. Idempotency ('calling it again returns the same asset') removes any need for the agent to guess about retries.

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

All Simpler.Asia 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?