Skip to main content
Glama

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

Get plan and credits

pixverse_get_features
Read-onlyIdempotent

Read one account's PixVerse plan live: plan_name, credit balances (credit_daily, credit_monthly, credit_package and the gift credits), refresh and expiry dates, gen_simultaneously (generations at once) and the image models and video qualities the plan allows. Use before a paid generation; pixverse_get_account shows only the stored settings. GET /features.

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_get_features"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoThe PixVerse account email, as pixverse_list_accounts shows it. Required when more than one account is configured.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), but the description adds real value beyond them: the read is 'live' rather than from stored settings, the exact content of the response is previewed, and the endpoint (GET /features) is disclosed. It does not mention rate limits, auth requirements, or error behavior, which keeps it below a 5.

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?

Two sentences, front-loaded with the core action and outcome, with no filler or restatement of the title. The field enumeration is dense but each item is informative since there is no output schema; the trailing 'GET /features' is the only mildly low-value fragment.

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?

With a single optional parameter, no output schema, and only generic annotations, the description carries the burden well by listing exactly what comes back and when to call it. An agent has everything needed to invoke this correctly and interpret the result.

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 100% and the single 'email' parameter is already fully documented in the schema, including the multi-account requirement and the pointer to pixverse_list_accounts. The description reinforces the per-account scoping ('one account's ... plan') but adds no new syntax or format detail, so the baseline 3 applies.

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 opens with a specific verb and resource ('Read one account's PixVerse plan live') and enumerates the concrete fields returned (plan_name, credit_daily/monthly/package, refresh/expiry dates, gen_simultaneously, allowed image models and video qualities). It also explicitly differentiates itself from the sibling pixverse_get_account, so an agent can pick between them without opening either schema.

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?

'Use before a paid generation' gives a clear triggering condition, and 'pixverse_get_account shows only the stored settings' implicitly routes the agent to the sibling for cached/configuration data. It stops short of an explicit when-not-to-use statement or of saying what to do if the live lookup fails, so it is strong but not exhaustive.

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