Skip to main content
Glama

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

List PixVerse accounts

pixverse_list_accounts
Read-onlyIdempotent

List the PixVerse accounts added to this useapi.net API token, as stored: email, maxJobs, session expiry and any pending account error. No call to PixVerse; pixverse_get_features shows a live plan and credits. Accounts are added on the setup page, not here. GET /accounts.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: this reads stored data with no round trip to PixVerse, which implies the values (including "session expiry" and "any pending account error") may be stale snapshots rather than live state. That staleness warning is the kind of context annotations cannot express.

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?

Four short sentences, front-loaded with what is listed, then the returned fields, then the alternative and the setup note. Nothing is redundant, and even the trailing "GET /accounts." endpoint hint is compact and useful for an API-aware agent.

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 compensates by naming the return fields (email, maxJobs, session expiry, pending error), and with zero parameters there is no input burden. The only gap is ordering or whether accounts are returned for multiple workspaces, which an agent might still wonder about, but overall it is sufficient to call correctly.

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?

The tool takes zero parameters, so there is no parameter meaning to add and the baseline of 4 applies. The description instead spends its words on the returned fields, which is a better use of the space.

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?

The description opens with a specific verb and resource ("List the PixVerse accounts") plus an explicit scope ("added to this useapi.net API token, as stored"), so an agent immediately knows this is a local token-scoped enumeration, not a live remote query. It does not distinguish itself from the very close sibling pixverse_get_account (singular), leaving the plural-vs-single split implicit.

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?

"No call to PixVerse; pixverse_get_features shows a live plan and credits" explicitly routes the agent to an alternative when live data is needed, and "Accounts are added on the setup page, not here" rules out a mistaken use as a creation tool. It gives clear context but no exclusion relative to pixverse_get_account, so it stops short of full when/when-not coverage.

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