Skip to main content
Glama

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

Get an account

pixverse_get_account
Read-onlyIdempotent

One account's stored settings: email, maxJobs, the PixVerse session's expiry (jwt.ExpireTimeUTC) and any pending error (such an account answers 596 until it is added again). No call to PixVerse; use pixverse_get_features for the live plan and credits, pixverse_list_accounts for every account. GET /accounts/{email}.

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": {
      "email": "<email>"
    },
    "name": "pixverse_get_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesThe account email.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds real value beyond them: it reads only locally stored data rather than hitting PixVerse, and it discloses that an account with a pending error answers 596 until re-added. It does not describe the failure payload shape or whether stale expiry data is refreshed, which keeps it from 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?

Front-loads the payload contents, then alternatives, then the underlying route in one dense but readable passage. The parenthetical about the 596 error is slightly cryptic, but no sentence is filler.

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?

For a single-account getter with no output schema, it gives enough: field list, local-vs-live data distinction, error condition, and sibling routing. Minor gaps remain around the 596 condition's resolution path and the exact response shape, but the essentials are covered.

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 parameter is documented there, so the baseline is 3. The description adds only that email is the identity key used in the GET /accounts/{email} path, which is marginal extra meaning.

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+resource ('One account's stored settings') and enumerates the fields returned (email, maxJobs, jwt.ExpireTimeUTC, pending error). It also names the sibling tools it is not (pixverse_get_features, pixverse_list_accounts), so an agent can distinguish it without reading schemas.

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 scopes itself negative-wise ('No call to PixVerse') and routes alternatives with conditions: live plan and credits go to pixverse_get_features, every account goes to pixverse_list_accounts. Nothing is left to inference.

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