Skip to main content
Glama

PixVerse MCP Server by useapi.net (third-party)

Get a speech clip

pixverse_get_speech
Read-onlyIdempotent

One speech clip from pixverse_create_speech or pixverse_list_speech: audio_status_name (QUEUED, GENERATING, COMPLETED, FAILED) and, once completed, the audio url, duration, voice and language; fail_reason when it failed. wait: true waits up to ~50 s. Music tracks are read with pixverse_get_music. GET /speech/{audio_id}.

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": {
      "audio_id": "<audio_id>"
    },
    "name": "pixverse_get_speech"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoWait up to ~50 s for the job to finish.
audio_idYesThe audio_id of a speech clip, e.g. user:12345-pixverse:you@example.com-speech:123456789 (it names the account).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the marginal burden is low. The description still adds real behavior beyond them: the status lifecycle values, the presence of fail_reason on failure, and the fact that wait: true blocks for roughly 50 seconds. It stops short of describing what happens when wait expires or whether re-calling is the intended polling pattern.

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?

It is dense and front-loaded: the return shape and the sibling distinction come before the wait semantics and the HTTP route. The colon-delimited fragment style is efficient but verges on telegraphic, and the trailing endpoint string adds little for an agent that invokes tools rather than HTTP.

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

Completeness4/5

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

With no output schema, the description correctly carries the return value story (statuses, url, duration, voice, language, fail_reason), which is what an agent most needs for a polling-style get. Its only notable gap is guidance on what to do when the status is still QUEUED or GENERATING without wait.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already documented and a baseline of 3 applies. The description adds meaning the schema lacks by tying audio_id to the tools that produce it and clarifying that wait: true corresponds to waiting for the job to finish, not just a transport timeout.

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 verb and resource (retrieve one speech clip) and immediately enumerates what comes back: audio_status_name with its four states, plus audio url, duration, voice, language, and fail_reason. It also distinguishes itself from pixverse_get_music, so an agent can separate speech retrieval from music retrieval without opening a schema.

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?

The description names where the audio_id originates (pixverse_create_speech or pixverse_list_speech), which is the key prerequisite for calling it, and explicitly routes music retrieval to pixverse_get_music instead. It also states when to set wait: true versus calling and polling implicitly.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources