Skip to main content
Glama
brandon-fryslie

elevenlabs-mcp

list_phone_numbers

Read-only

Retrieve all phone numbers linked to your ElevenLabs account for managing call settings or verifying ownership.

Instructions

List all phone numbers associated with the ElevenLabs account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes
textYes
annotationsNo
_metaNo

Implementation Reference

  • Registration of the 'list_phone_numbers' tool via @mcp.tool decorator with readOnlyHint and description.
    @mcp.tool(
        annotations=ToolAnnotations(readOnlyHint=True, openWorldHint=True),
        description="List all phone numbers associated with the ElevenLabs account"
    )
  • Handler function that calls client.conversational_ai.phone_numbers.list() and formats the results.
    def list_phone_numbers() -> TextContent:
        """List all phone numbers associated with the ElevenLabs account.
    
        Returns:
            TextContent containing formatted information about the phone numbers
        """
        response = client.conversational_ai.phone_numbers.list()
    
        if not response:
            return TextContent(type="text", text="No phone numbers found.")
    
        phone_info = []
        for phone in response:
            assigned_agent = "None"
            if phone.assigned_agent:
                assigned_agent = f"{phone.assigned_agent.agent_name} (ID: {phone.assigned_agent.agent_id})"
    
            phone_info.append(
                f"Phone Number: {phone.phone_number}\n"
                f"ID: {phone.phone_number_id}\n"
                f"Provider: {phone.provider}\n"
                f"Label: {phone.label}\n"
                f"Assigned Agent: {assigned_agent}"
            )
    
        formatted_info = "\n\n".join(phone_info)
        return TextContent(type="text", text=f"Phone Numbers:\n\n{formatted_info}")
Behavior3/5

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

Annotations provide readOnlyHint=true and openWorldHint=true, covering safety and data volatility. The description adds no behavioral details beyond what annotations declare, providing minimal extra value.

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?

Single sentence, front-loaded verb 'List', no wasted words. Perfectly concise and structured.

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?

Given zero parameters, rich annotations, and presence of output schema, the description is adequate. It does not mention the output explicitly, but output schema compensates.

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?

No parameters exist, and schema coverage is 100%. Baseline score of 4 applies as description need not compensate for missing parameter documentation.

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?

Description clearly states verb 'list', resource 'phone numbers', and scope 'associated with the ElevenLabs account'. Distinguishes from sibling list tools (e.g., list_agents, list_conversations) by specifying a unique resource.

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?

No explicit guidance on when to use this tool versus alternatives. Usage is implied by the purpose but lacks context, such as linking to related tools like make_outbound_call that might rely on phone numbers.

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/brandon-fryslie/vibedungeon-voice'

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