Skip to main content
Glama

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

List speech clips

pixverse_list_speech
Read-onlyIdempotent

One account's speech clips: audio_id, status, voice, language and audio url, a page at a time; pass next_offset as offset for the next page while has_more. Music tracks are listed by pixverse_list_music. GET /speech.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pixverse_list_speech"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoThe PixVerse account email, as pixverse_list_accounts shows it. Required when more than one account is configured.
limitNoItems per page (default 50).
offsetNoWhere the page starts (default 0): the next_offset of the previous page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real behavioral context beyond that: the paging contract (has_more plus next_offset reuse) and the underlying GET /speech endpoint, which tells the agent this is a plain read with no side effects.

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?

A single dense sentence front-loads the resource and returned fields, then tacks on the paging rule and the sibling pointer. No filler, and the most decision-relevant information comes first.

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 compensates by listing the returned fields, and it explains pagination end-to-end. Minor gaps remain, such as ordering of results or whether status values are enumerable, but nothing needed to invoke the tool correctly is missing.

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 the baseline is 3, but the description adds the loop condition ('while has_more') that the schema does not state, clarifying how offset and the returned next_offset interact. The email parameter's multi-account requirement is left to the schema, which already documents it.

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 (list one account's speech clips) and enumerates the returned fields (audio_id, status, voice, language, audio url), so the agent knows exactly what comes back. It also explicitly separates itself from pixverse_list_music, which lists music tracks instead.

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

Usage Guidelines4/5

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

Names the sibling alternative for music and gives concrete pagination instructions ('pass next_offset as offset for the next page while has_more'). It does not spell out when to prefer this over pixverse_get_speech for a single clip, but the list-vs-get distinction is implied by the paging language.

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