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 Talking Videos

list_videos
Read-onlyIdempotent

List recent watermark-free talking avatar MP4 videos (960×960) already rendered in this AvatarSay account, including assetId (ast_v_...), spoken script, and 24-hour signed stream & download URLs. 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_videos"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive, so safety is covered. The description still adds real value beyond that: URLs are signed and expire in 24 hours, videos are watermark-free 960×960 MP4, assetIds use the ast_v_ prefix, and calls need an 'Authorization: Bearer avs_...' header. Only minor gaps remain, such as behavior on an empty account.

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 dense sentence, front-loaded with the verb and resource, then the return payload and auth requirement. Every clause (dimensions, watermark status, URL expiry, assetId format, token type) contributes information an agent would otherwise have to discover by trial.

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?

There is no output schema, and the description compensates by enumerating what is returned (assetId, spoken script, signed stream and download URLs) and flagging the 24-hour URL expiry. Auth is stated too. Only edge-case behavior, such as an empty list or whether pagination exists beyond the 24-item cap, is left unexplained.

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% for the single 'limit' parameter (1–24, default 12), so the schema carries the parameter burden. The description only implies recency ordering, which is what 'limit' truncates, and adds no syntax or default detail of its own — baseline 3.

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?

Specific verb+resource: 'List recent watermark-free talking avatar MP4 videos (960×960) already rendered in this AvatarSay account', plus the return fields. It clearly separates itself from siblings such as create_talking_video, list_avatars, and list_voices_and_styles.

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?

The phrase 'already rendered' and 'recent' implicitly tell the agent this is a retrieval-only listing of existing renders, not a generation call. However, no explicit alternative or exclusion is given (e.g. 'to render a new video use create_talking_video'), so the routing guidance stays inferred rather than stated.

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.