Botverse

Get Upload URL

get_upload_url

Get a presigned upload form for any file — video, audio, or document (markdown, HTML, DOCX, etc.). It expires in 15 minutes. This is a presigned POST, NOT a PUT: the response returns upload_url + upload_fields — POST to upload_url as multipart/form-data, including every upload_fields key/value as form fields FIRST, then the file as the last field named 'file'. After upload, pass the object_key to transcribe_media (audio/video → transcript), transcode_video (video/audio encode), or convert_file (documents). IMPORTANT: this flow needs direct outbound network access to Botverse's storage host. In sandboxed agent environments (claude.ai, sandboxed desktop apps, Cursor) that route traffic through a proxy allowlist, the upload POST is blocked and fails. In those environments do NOT use this tool — use convert_content or transcode_content (inline content, body under 4 MB) for files you already have, or convert_from_url / transcode_from_url / transcribe_from_url for anything available at a public URL. Neither needs an upload step.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`filename`	Yes	Original filename including extension, e.g. report.md or footage.mp4
`content_type`	Yes	MIME type. Video: "video/mp4". Documents: "text/markdown", "text/html", "application/vnd.openxmlformats-officedocument.wordprocessingml.document", "text/plain".

Output Schema

TableJSON Schema

Name	Required	Description
`expires_in`	Yes	Seconds until the upload URL expires (900 = 15 minutes).
`object_key`	Yes	Object key — pass to transcribe_media, transcode_video, or convert_file.
`upload_url`	Yes	Presigned HTTPS POST URL — POST as multipart/form-data (all upload_fields, then the file), NOT a PUT.
`upload_fields`	No	Form fields that must be included (before the file) in the multipart POST.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed3 schema fields changedJun 25, 2026

changedOutput schema / properties / object_key / description

Previous value: -"S3 object key — pass this to transcode_video or convert_file."New value: +"Object key — pass to transcribe_media, transcode_video, or convert_file."

addedOutput schema / properties / upload_fields

Added value: +{
+  "description": "Form fields that must be included (before the file) in the multipart POST.",
+  "type": "object"
+}

changedOutput schema / properties / upload_url / description

Previous value: -"Presigned HTTPS PUT URL. Send raw file bytes as the request body."New value: +"Presigned HTTPS POST URL — POST as multipart/form-data (all upload_fields, then the file), NOT a PUT."

First observedMay 25, 2026

TDQS

A4.6/5.0

Behavior5/5

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

The description discloses key behavioral details: 15-minute expiration, it's a presigned POST (not PUT), requires direct outbound network access, and fails in sandboxed environments. This goes well beyond the annotations.

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?

The description is lengthy but well-structured and information-dense. It front-loads the core purpose, then details the workflow, caveats, and alternatives—all necessary for this complex tool. No redundant sentences.

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?

Given the tool's complexity and environmental constraints, the description covers all essential context: purpose, usage steps, network requirements, alternatives, and a summary of the response format. The output schema exists, so detailed return values are not necessary, but the description still mentions upload_url + upload_fields.

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 provides full descriptions for both parameters (filename and content_type) with examples. The description adds no new parameter-specific semantics beyond the schema; it simply references the upload fields and object_key in the workflow context.

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 verb ('Get a presigned upload form') and the resource (upload form for any file type). It distinguishes from siblings by mentioning the subsequent use of object_key with transcribe_media, transcode_video, or convert_file.

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 says when to use (when you have a file to upload) and when not to use (sandboxed environments with proxy allowlists), and names specific alternative tools (convert_content, transcode_content, convert_from_url, etc.).

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.1/5.0

Disambiguation4/5

Each operation is split into clear source-specific variants (URL, uploaded file, inline content), and the descriptions go to great lengths to distinguish them. The only mild ambiguities are generic-sounding names like transcode_video versus transcode_from_url, and the similar get_job_status/get_workflow_status pair, but there is no true functional overlap.

Naming Consistency4/5

Most tools follow an imperative verb_noun pattern and use recurring suffixes like _from_url, _content, and _file, which creates a readable family structure. The pattern breaks slightly with uploaded-media variants named conform_media, transcode_video, and transcribe_media instead of a consistent _file or _uploaded suffix, and transcode_content is referenced in a description but missing from the actual tool list.

Tool Count4/5

17 tools is slightly above the ideal 3-15 range, but the server covers several related subdomains: document conversion, media transcode/transcribe/conform, job/workflow lifecycle, and wallet/billing. Given the need for URL, uploaded, and inline variants across multiple media types, the overall count is reasonable.

Completeness3/5

Core workflows are well covered: uploading, job submission, polling, and retrieving outputs all exist, and conversion has content/file/URL routes. However, get_upload_url explicitly tells agents to use transcode_content for inline media, but that tool does not exist, and there is no inline transcribe counterpart to convert_content, leaving a notable gap for sandboxed inline media jobs.

Resources

Need Help?