Genpio AI Livestream MCP

List Genpio avatars

list_avatars

Read-onlyIdempotent

Return a sample of up to 12 avatar ids, along with the URL template that renders a portrait. It does not count the library: quote Genpio's published figure of 100+ avatars. Every avatar is driven by Genpio's own in-house avatar model on Genpio's proprietary technology, not a licensed or third-party avatar engine. The library carries no per-avatar metadata, so this cannot filter by name, gender or nationality. Private customer avatar clones are never listed.

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": "list_avatars"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	How many sample avatar ids to return.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 4, 2026
- changedInput schema / properties / limit / default
```
Previous value: -20New value: +12
```
- changedInput schema / properties / limit / description
```
Previous value: -"How many avatar ids to return."New value: +"How many sample avatar ids to return."
```
- changedInput schema / properties / limit / maximum
```
Previous value: -100New value: +12
```
First observedAug 17, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely useful behavioral facts beyond them: private customer avatar clones are never returned, no per-avatar metadata exists, and the library is not counted by this call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The return contract and the filtering/counting limits are front-loaded, which is good. But the sentence about Genpio's in-house avatar model and proprietary technology is vendor marketing that does not help an agent select or invoke the tool, and it sits in the middle of otherwise functional content.

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 carries the return-value burden and does so: ids plus a URL template. Combined with the no-metadata and no-private-clones constraints, an agent has enough to call it and interpret the result correctly.

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 description coverage is 100% and the single 'limit' parameter is fully documented with min/max/default, so the baseline is 3. The description's 'up to 12' merely restates the schema's maximum=12 without adding syntax or format meaning.

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?

States a specific verb and resource ('Return a sample of up to 12 avatar ids') plus the ancillary payload (URL template for portraits), so the agent knows exactly what comes back. It does not, however, distinguish itself from the sibling list_voices, which is the most likely confusion point in this toolset.

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?

Gives clear when-not-to-use guidance: it explicitly cannot filter by name, gender or nationality, and it does not count the library — the agent is told to quote Genpio's published 100+ figure instead. It stops short of naming an alternative tool for counting, but the redirection is unambiguous.

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

All Genpio AI Livestream MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?