Skip to main content
Glama

AvatarSay — Fictional Character, RPG NPC & Talking Video MCP

This connector has been deprecated

Replaced by AvatarSay.

Consolidated into the primary verified AvatarSay connector com.avatarsay/avatar-say.

List Account Character Avatars

list_avatars
Read-onlyIdempotent

List recent fictional character avatars (both AI-generated portraits and imported stylized character illustrations) in this AvatarSay account, including assetId (ast_...) and 24-hour signed download URLs, ready to animate with create_talking_video. Requires Authorization: Bearer avs_...

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

NameRequiredDescriptionDefault
limitNoMaximum number of recent avatar images to return (1–24, default 12).

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 cover read-only, idempotent, non-destructive, closed-world semantics, yet the description adds real value: it discloses the required 'Authorization: Bearer avs_...' credential and warns that download URLs are 24-hour signed links, which is operationally important. It stops short of describing ordering, empty-account behavior, or whether unpinned avatars expire.

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?

One front-loaded sentence carries the resource, scope, return contents, downstream use, and auth requirement with no filler. Dense but every clause earns its place and nothing is repeated.

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 no output schema, the description compensates by naming what comes back (assetId and signed download URLs) and their expiry. Auth, scope, and follow-on tool are all covered, so an agent has everything needed to invoke it 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?

The single 'limit' parameter is fully documented in the schema (1–24, default 12), so schema coverage is 100%. The description adds nothing about it, which is acceptable at the baseline but leaves no extra meaning to add.

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 ('List'), resource ('recent fictional character avatars'), and scope ('in this AvatarSay account'), and clarifies that both AI-generated and imported portraits are included — which implicitly distinguishes it from generate_avatars and import_character_portrait. The assetId shape (ast_...) further pins down what is returned.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: 'ready to animate with create_talking_video' signals the downstream step, but the description never says when to call this instead of generate_avatars or import_character_portrait, nor any precondition besides auth. An agent can infer the retrieve-then-animate flow but not the exclusion rules.

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.