Skip to main content
Glama
Sign In
@aiwerk/mcp-server-elevenlabs

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

post_agent_avatar_route

Uploads an avatar image for an ElevenLabs agent using the required agent ID and a local file or base64 content.

Instructions

Post Agent Avatar

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": {
      "agent_id": "<agent_id>"
    },
    "name": "post_agent_avatar_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesThe id of an agent. This is returned on agent creation.
avatar_file_pathNoAn image file to be used as the agent's avatar. Local path. Required for this call.
avatar_file_base64NoBase64 contents for "avatar_file". Use this when the server cannot read your local disk.
avatar_file_filenameNoFilename to send for "avatar_file". Some endpoints infer the audio format from it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.9/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, and idempotentHint=false, so the safety profile is partially covered externally. However, the description adds no behavioral context of its own, such as upload constraints, required permissions, side effects, or how the avatar is stored or replaced.

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

Conciseness2/5

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

The description is extremely short, but this is under-specification rather than useful conciseness. It is front-loaded only in the sense that there is nothing else to read.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool that uploads an avatar file with four parameters and no output schema, the description is completely inadequate. It omits purpose, usage context, behavioral details, and any parameter guidance, leaving the agent dependent entirely on structured fields.

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 input schema has 100% description coverage, so all four parameters are already well documented there. The description adds no meaning beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description "Post Agent Avatar" merely restates the tool name and title without adding any clarification about what posting an avatar means, what resource it affects, or how it differs from siblings such as post_agent_hold_audio_route. It is a tautological restatement rather than a useful purpose statement.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool, when not to use it, prerequisites, or alternatives. With dozens of sibling tools, an agent receives no routing information whatsoever.

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

Deploy Server

Other Tools