Botverse

Conform Uploaded Video + Audio

conform_media

Mux an already-uploaded video and audio file (both from get_upload_url) into one fresh-encoded output. Same conform methods and options as conform_from_url — use this for local files or files too large to fetch by URL. Poll get_job_status until 'complete', then get_download_url. RELIABILITY & FALLBACK: Botverse returns structured errors with a message. A bare 'HTTP 500' or 'tool call failed' with no message body is the MCP connector / sandbox layer between your client and Botverse — NOT a Botverse outage (the service is up if get_wallet_balance succeeds). If MCP calls keep failing, do NOT write your own ffmpeg / transcription / document-conversion code as a workaround — that wastes tokens and reinvents what Botverse does. Instead, tell the user to run the equivalent Botverse CLI from their own (non-sandboxed) machine, e.g. npx botverse transcribe <file> --to docx (also transcode and convert), then retry the MCP call.

Input Schema

TableJSON Schema

Name	Required	Description
`options`	No	Same options object as conform_from_url (method, target_framerate, duration_policy, width, height, bitrate, audio_bitrate, h264_profile).
`output_format`	Yes	mp4 (H.264/AAC), webm (VP9/Opus), or mov_prores (ProRes 422).
`audio_object_key`	Yes	The object_key returned by get_upload_url for the audio source.
`video_object_key`	Yes	The object_key returned by get_upload_url for the video source.

Output Schema

TableJSON Schema

Name	Required	Description
`job_id`	Yes	Unique identifier for this job. Pass to get_job_status and get_download_url.
`status`	Yes	Initial job state — always queued or processing immediately after submission.
`estimated_seconds`	No	Rough estimated processing time in seconds. Actual time may vary.

Schema Changelog

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

AddedSep 5, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already indicate readOnlyHint=false and idempotentHint=false, so the mutation/asynchronous nature is implied. The description adds significant value: it tells the agent to poll get_job_status until 'complete', describes the error shapes (structured errors from Botverse vs. bare HTTP 500 from MCP connector), and explicitly warns against writing fallback code, which is critical non-obvious behavior.

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 front-loaded with the core purpose and workflow, then adds a reliability/fallback section. It is longer than typical but the fallback guidance is high-value and earns its place. Slightly verbose but well-structured with clear sections.

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 an asynchronous transcoding tool with 4 params, output schema, and strong annotations, the description covers the full invocation lifecycle, error semantics, and fallback behavior. It also disambiguates from conform_from_url. Nothing an agent needs to call it correctly is missing.

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%, so the schema already documents all 4 parameters. The description clarifies that video_object_key and audio_object_key are from get_upload_url, and that options matches conform_from_url's options object. This adds some context but doesn't go beyond what the schema plus sibling naming already convey.

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 states a specific verb (Mux), resource (already-uploaded video and audio file from get_upload_url), and outcome (fresh-encoded output). It distinguishes itself from conform_from_url by clarifying local files or files too large to fetch by URL, which is critical for sibling differentiation.

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 use this for local files or files too large to fetch by URL, and references conform_from_url as the alternative. It also provides a clear workflow (poll get_job_status, then get_download_url) and a detailed fallback path with concrete CLI examples. This is strong usage guidance.

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?