Skip to main content
Glama
elevenlabs

ElevenLabs MCP Server

Official
by elevenlabs

simulate_conversation

Run a simulated text conversation between your AI agent and a user persona to test behavior, evaluate prompts, and catch failure modes without a live call.

Instructions

Simulate a text conversation between a conversational AI agent and a simulated user. Runs the full conversation and returns the transcript plus analysis.

Use this to test agent behaviour, evaluate prompts, and catch failure modes without
a live call. The simulated user follows the persona you describe.

⚠️ COST WARNING: This tool makes an API call to ElevenLabs which may incur costs.
Only use when explicitly requested by the user.

Args:
    agent_id: ID of the agent to test. Use list_agents to find IDs.
    simulated_user_prompt: Instructions for how the simulated user should behave.
        Example: "You are a frustrated customer who cannot find the cancel button."
    first_message: Optional opening message to kick off the conversation.
    extra_evaluation_criteria: Optional list of dicts, each with:
        - id (str): unique key e.g. "issue_resolved"
        - name (str): human label e.g. "Issue Resolved"
        - conversation_goal_prompt (str): the assertion to check
          e.g. "The agent fully resolved the user's issue."
        - use_knowledge_base (bool, optional): whether the evaluator should
          reference the agent's knowledge base when judging. Defaults to False.
    max_turns: Maximum conversation turns. Defaults to 10.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idYes
max_turnsNo
first_messageNo
simulated_user_promptYes
extra_evaluation_criteriaNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
typeYes
_metaNo
annotationsNo
Behavior5/5

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

Discloses that the tool makes an API call to ElevenLabs which may incur costs, and describes the full process of running the conversation and returning transcript plus analysis. Annotations (openWorldHint, destructiveHint) are consistent; no contradictions.

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

Conciseness4/5

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

The description is well-structured with clear sections (args, warning) and examples, but is slightly verbose. Every sentence adds value, though could be trimmed slightly without losing substance.

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?

Given the 5 parameters and existence of an output schema, the description covers all necessary details: purpose, usage, parameter semantics, and behavioral context. It is fully complete for an agent to correctly select and invoke the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by explaining each parameter: agent_id, simulated_user_prompt (with example), first_message, extra_evaluation_criteria (with structure and example), and max_turns (default 10). Adds significant meaning beyond the schema.

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 clearly states the tool simulates a text conversation between an AI agent and a simulated user, returning transcript and analysis. It distinguishes from sibling tools like make_outbound_call and list_conversations by focusing on testing without a live call.

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

Usage Guidelines5/5

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

Explicitly states when to use: 'test agent behaviour, evaluate prompts, and catch failure modes without a live call.' Includes a cost warning and instructs 'Only use when explicitly requested by the user,' providing clear usage boundaries.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/elevenlabs/elevenlabs-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server