Skip to main content
Glama
brandon-fryslie

elevenlabs-mcp

get_agent

Read-only

Retrieve detailed information about a specific conversational AI agent by providing its agent ID. Access configuration, capabilities, and metadata to manage or integrate the agent.

Instructions

Get details about a specific conversational AI agent

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes
textYes
annotationsNo
_metaNo

Implementation Reference

  • Handler function that executes the 'get_agent' tool logic. It calls the ElevenLabs conversational AI API to get agent details by ID, extracts voice configuration info, and returns a formatted TextContent response with agent name, ID, voice config, and creation timestamp.
    @mcp.tool(
        annotations=ToolAnnotations(readOnlyHint=True, openWorldHint=True),
        description="Get details about a specific conversational AI agent"
    )
    def get_agent(agent_id: str) -> TextContent:
        """Get details about a specific conversational AI agent.
    
        Args:
            agent_id: The ID of the agent to retrieve
    
        Returns:
            TextContent with detailed information about the agent
        """
        response = client.conversational_ai.agents.get(agent_id=agent_id)
    
        voice_info = "None"
        if response.conversation_config.tts:
            voice_info = f"Voice ID: {response.conversation_config.tts.voice_id}"
    
        return TextContent(
            type="text",
            text=f"Agent Details: Name: {response.name}, Agent ID: {response.agent_id}, Voice Configuration: {voice_info}, Created At: {datetime.fromtimestamp(response.metadata.created_at_unix_secs).strftime('%Y-%m-%d %H:%M:%S')}",
        )
  • Registration of 'get_agent' as an MCP tool via the @mcp.tool decorator on the FastMCP instance, with read-only and open-world hints.
    @mcp.tool(
        annotations=ToolAnnotations(readOnlyHint=True, openWorldHint=True),
        description="Get details about a specific conversational AI agent"
Behavior2/5

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

Annotations already provide readOnlyHint=true and openWorldHint=true, so the description adds little behavioral context. It does not clarify what 'details' include, nor mention any rate limits, authentication requirements, or potential side effects. Given annotations cover most safety aspects, the description should add value beyond that.

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

Conciseness3/5

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

The description is a single sentence, which is concise but very brief. For a tool with zero parameter documentation, more detail would be warranted. It is not verbose but could be more informative without increasing length significantly.

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

Completeness3/5

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

Given the tool has an output schema (not shown), the description might be sufficient for a basic get operation. However, the lack of parameter semantics and usage guidelines, combined with sibling tools, means the agent may need additional information to use it correctly. The openWorldHint annotation adds some context, but overall it is minimally complete.

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

Parameters2/5

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

Schema description coverage is 0%, meaning the input schema provides no description for the agent_id parameter. The description does not explain what agent_id refers to (e.g., format, where to find it). Since the parameter is required and the only input, this is a significant gap.

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 the tool retrieves details about a specific conversational AI agent. The verb 'Get' and resource 'details about a specific conversational AI agent' are precise, and it distinguishes from sibling tools like list_agents (which lists all agents) and create_agent.

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 versus siblings. The name implies use when an agent_id is known, but it does not mention alternatives like list_agents for browsing or create_agent for new agents. Usage context is only implied.

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