Skip to main content
Glama
Venice MCP Server

Venice MCP Server

Official
by veniceai

Venice Music Retrieve / Status

venice_music_status
DestructiveIdempotent

Check the status of a queued music generation job, returning JSON progress while processing and completed audio as an embedded resource or download URL.

Instructions

Check status of a queued music job. Returns JSON progress while PROCESSING. Completed jobs are either an embedded base64 audio MCP resource or a download_url resource link. POST endpoint with body {model, queue_id}. Supports x402 wallet auth (no Venice account needed) and API key.

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": {
      "queue_id": "<queue_id>",
      "model": "<model>"
    },
    "name": "venice_music_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYes
queue_idYes
delete_media_on_completionNoDelete server-side media after embedded audio has been buffered, before the tool result returns to the client. Ignored for download_url results: download first, then call venice_music_complete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.1
    • changedInput schema / properties / delete_media_on_completion / description
      Previous value: -"Delete server-side media once embedded audio has been buffered. Ignored for download_url results: download first, then call venice_music_complete."New value: +"Delete server-side media after embedded audio has been buffered, before the tool result returns to the client. Ignored for download_url results: download first, then call venice_music_complete."
  2. Changed1 schema field changedv0.3.0
    • addedInput schema / properties / delete_media_on_completion / description
      Added value: +"Delete server-side media once embedded audio has been buffered. Ignored for download_url results: download first, then call venice_music_complete."
  3. First observedv0.2.0

TDQS

A3.6/5.0
Behavior4/5

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

Adds real context beyond the annotations: it discloses the transport (POST with body {model, queue_id}), the intermediate return shape (JSON progress while PROCESSING), the two terminal shapes (embedded base64 resource vs download_url link), and the auth options (x402 wallet or API key). It does not explain why destructiveHint=true — i.e., that media can be deleted server-side — so the destructive profile is left to 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?

Four short clauses, front-loaded with the core action, then return shapes, then transport, then auth. No filler, though the auth clause is slightly tangential to a status check and could be trimmed.

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

Completeness3/5

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

There is no output schema, so the description must carry the return contract, and it does describe the PROCESSING and completed shapes reasonably well. It omits failure/expiry states, polling cadence, and the consequences of the destructive flag, which matter for a queue-status tool.

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 coverage is only 33%, and the description partly compensates by stating the request body is {model, queue_id} and that download_url results need a separate fetch step. It still doesn't clarify what model means for a status lookup (must it match the enqueue-time model?) or the media-deletion lifecycle, leaving a gap against the low coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: 'Check status of a queued music job.' An agent can distinguish this from venice_music_generate (which enqueues) and venice_music_complete, though neither sibling is named explicitly in the description.

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

Usage Guidelines3/5

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

Usage is implied by 'queued music job' and by the note that completed jobs return audio or a download_url, which tells the agent this is a polling tool. However, it never states when to call it (after venice_music_generate), how often to poll, or when to hand off to venice_music_complete instead — that routing only appears inside the schema for delete_media_on_completion.

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