Skip to main content
Glama

retell_list_agents

Retrieve all configured voice agents from your Retell AI account to manage and deploy AI phone agents.

Instructions

List all voice agents in your Retell account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation for the 'retell_list_agents' tool. Executes a GET request to the Retell API endpoint '/list-agents' using the shared retellRequest helper.
    case "retell_list_agents":
      return retellRequest("/list-agents", "GET");
  • src/index.ts:518-525 (registration)
    Tool registration entry in the tools array, including name, description, and empty input schema (no parameters required). This is returned by the ListTools handler.
    {
      name: "retell_list_agents",
      description: "List all voice agents in your Retell account.",
      inputSchema: {
        type: "object",
        properties: {}
      }
    },
  • Input schema for retell_list_agents tool, defining an empty object (no required arguments).
    inputSchema: {
      type: "object",
      properties: {}
    }
  • Shared helper function used by all Retell tools, including retell_list_agents, to make authenticated HTTP requests to the Retell API.
    async function retellRequest(
      endpoint: string,
      method: string = "GET",
      body?: Record<string, unknown>
    ): Promise<unknown> {
      const apiKey = getApiKey();
    
      const headers: Record<string, string> = {
        "Authorization": `Bearer ${apiKey}`,
        "Content-Type": "application/json",
      };
    
      const options: RequestInit = {
        method,
        headers,
      };
    
      if (body && method !== "GET") {
        options.body = JSON.stringify(body);
      }
    
      const response = await fetch(`${RETELL_API_BASE}${endpoint}`, options);
    
      if (!response.ok) {
        const errorText = await response.text();
        throw new Error(`Retell API error (${response.status}): ${errorText}`);
      }
    
      // Handle 204 No Content
      if (response.status === 204) {
        return { success: true };
      }
    
      return response.json();
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions 'List all' but doesn't disclose behavioral traits like whether this is a read-only operation, if it requires authentication, potential rate limits, or the format of returned data. For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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?

The description is a single, front-loaded sentence that directly states the tool's purpose without any unnecessary words. It's appropriately sized for a simple list operation, making it easy to parse and understand immediately.

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's simplicity (0 parameters, no output schema), the description is adequate but not complete. It lacks details on behavioral aspects like authentication needs, response format, or pagination, which would be helpful for an AI agent to use it correctly. Without annotations or output schema, more context would improve completeness.

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?

The tool has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description doesn't add parameter semantics, but this is appropriate given the lack of parameters. A baseline of 4 is assigned as the description doesn't need to compensate for any parameter gaps.

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 specific action ('List all') and resource ('voice agents in your Retell account'), making the purpose immediately understandable. It distinguishes this tool from siblings like 'retell_get_agent' (which retrieves a single agent) and 'retell_list_chat_agents' (which lists a different type of agent), providing precise scope.

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?

The description implies usage for retrieving all voice agents, but doesn't explicitly state when to use this versus alternatives like 'retell_get_agent' for specific agents or 'retell_list_chat_agents' for chat agents. No guidance on prerequisites, pagination, or rate limits is provided, leaving usage context incomplete.

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/itsanamune/retellsimp'

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