Botverse

Get Download URL

get_download_url

Read-onlyIdempotent

Get a presigned HTTPS URL to download the completed output file. Call after get_job_status returns 'complete'. URL expires in 24 hours. NOTE: fetching this URL is a direct S3 download, which is BLOCKED in sandboxed agent environments (claude.ai, Claude Desktop, Cursor). If you are in a sandbox, use get_output_content instead to receive the bytes inline over the tool channel.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`job_id`	Yes	Job ID from transcode_video, transcode_from_url, or any convert tool.

Output Schema

TableJSON Schema

Name	Required	Description
`filename`	Yes	Suggested filename for the downloaded file including extension.
`expires_at`	Yes	ISO 8601 timestamp when the download URL expires.
`size_bytes`	No	File size of the output in bytes.
`download_url`	Yes	Presigned HTTPS GET URL for the output file. Valid for 24 hours.

TDQS

A4.7/5.0

Behavior5/5

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

Discloses URL expiration (24 hours) and the direct S3 download limitation in sandboxed agent environments, which is beyond the readOnlyHint and idempotentHint annotations. No contradiction with annotations.

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 sentences, front-loaded with the primary action, followed by timing and a critical caveat. No filler or repetition.

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?

The tool's simplicity (single parameter) and rich annotations make the description sufficient. It covers the usage sequence, expiry, and sandbox workaround, which are the key contextual pieces.

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?

The input schema already documents job_id with complete provenance from transcode_video, transcode_from_url, or any convert tool. The description adds no further parameter-level detail, so baseline 3 for full schema coverage.

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?

The description clearly states the tool's function: getting a presigned HTTPS URL to download the completed output file. It distinguishes itself from siblings like get_output_content by specifying the URL-based download mechanism.

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?

Explicitly instructs when to call (after get_job_status returns 'complete') and provides a clear alternative for sandboxed environments (get_output_content). This directly addresses when to use vs alternatives.

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

All Botverse tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation4/5

Tools are largely distinguishable by their action and input source (content/file/url), but the multiple convert_* and transcode/transcribe variants overlap in purpose, and get_job_status vs get_workflow_status could cause confusion. Descriptions are thorough enough to guide selection, but the boundaries between similar actions are not always crisp.

Naming Consistency4/5

All names use snake_case with a verb-noun pattern (get_, convert_, transcode_, transcribe_, submit_, cancel_), which is consistent. However, the variant naming is not perfectly parallel: convert_content/file/from_url use a source suffix, whereas transcode_video vs transcode_from_url and transcribe_media vs transcribe_from_url mix output type and source, creating minor inconsistency.

Tool Count4/5

At 15 tools, the server is at the upper end of a well-scoped set. Each tool supports a distinct input/output route or workflow function, but the count is slightly heavy due to multiple variants of similar operations. It remains appropriate for the breadth of conversion, transcoding, transcription, workflow, and wallet features.

Completeness3/5

The core job lifecycle (submit, poll, retrieve output) is well covered, and workflows have submit/status/cancel. However, get_upload_url references a transcode_content tool that does not exist in the toolset, and there is no way to cancel a single job (only full workflows). This leaves gaps for inline media transcoding in sandboxed environments and granular job control.

Resources

Need Help?