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.

Create Lip-Synced Talking Character Video

create_talking_video

Animate an AvatarSay character avatar (ast_...) with lip-synced English speech in one of 8 preset voices. New accounts get their first short talking clip (<=5s / <=75 chars) for 0 credits! Subsequent or longer clips cost 12 account credits per second of speech (minimum 5s = 60 credits, maximum 30s). Enqueues asynchronously and returns jobId immediately — never blocks for the 3–5 minute render. Poll get_job every 20–30 seconds for the watermark-free 960×960 MP4 URL. Failed renders refund credits automatically. Requires Authorization: Bearer avs_...

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": {
      "assetId": "<assetId>",
      "script": "<script>",
      "voice": "<voice>"
    },
    "name": "create_talking_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
voiceYesBuilt-in English voice ID: Friendly_Person, Wise_Woman, Lively_Girl, Calm_Woman, Casual_Guy, Deep_Voice_Man, Patient_Man, Young_Knight.
scriptYesEnglish spoken dialogue line (2–400 chars, up to 30 seconds of speech; <=75 chars qualifies for the 0-credit first clip on new accounts).
assetIdYesAvatarSay character asset ID (ast_...) from generate_avatars -> get_job, import_character_portrait, or list_avatars. Camera photos of real people are not supported.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / assetId / description
      Previous value: -"AvatarSay image asset ID (ast_...) from generate_avatars -> get_job or list_avatars. Photo uploads are not supported."New value: +"AvatarSay character asset ID (ast_...) from generate_avatars -> get_job, import_character_portrait, or list_avatars. Camera photos of real people are not supported."
  2. Changed1 schema field changed
    • changedInput schema / properties / script / description
      Previous value: -"English spoken dialogue line (2–400 chars, up to 30 seconds of speech)."New value: +"English spoken dialogue line (2–400 chars, up to 30 seconds of speech; <=75 chars qualifies for the 0-credit first clip on new accounts)."
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false), the description discloses the credit pricing model (12 credits/second, 5s minimum = 60 credits, 30s maximum, free first short clip), the automatic refund on failed renders, the 3-5 minute render time, and the Bearer avs_ auth scheme. These are exactly the behavioral facts an agent needs before committing credits to a non-idempotent write.

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 tight sentences, front-loaded with what the tool does and its pricing, then the async/polling mechanics, then auth. Every clause carries operational information (cost, timing, polling interval, refund policy) with no restatement of the name or title.

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?

There is no output schema, but the description compensates fully by stating that a jobId is returned immediately and that get_job yields the watermark-free 960×960 MP4 URL, plus the failure/refund path. For a 3-parameter async generation tool, nothing an agent needs to call it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3. The description adds meaning the schema does not carry directly: the cost consequence of script length (minimum 5s = 60 credits, 30s ceiling) and the count of available voices, which helps an agent reason about pricing when choosing script size. It does not add syntax detail beyond the schema, so it sits just above baseline.

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?

The description names a specific verb and resource: animate an AvatarSay character avatar (ast_...) with lip-synced English speech using one of 8 preset voices. The async job model and the output format (960×960 watermark-free MP4) further pin down what the tool produces, so an agent can distinguish it from siblings like create_npc_voice_line or generate_avatars without opening a schema.

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?

The description gives clear operating context: it enqueues asynchronously and returns a jobId, so the agent should poll get_job every 20-30 seconds rather than block. It also names the prerequisite chain for assetId (generate_avatars -> get_job, import_character_portrait, list_avatars) and the auth requirement. It stops short of explicitly stating when to prefer create_npc_voice_line or list_videos instead, so it is strong but not complete routing guidance.

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.