Skip to main content
Glama

retell_get_call

Retrieve call details including transcript, recording URL, duration, and analysis from Retell AI's voice agent platform.

Instructions

Retrieve details of a specific call including transcript, recording URL, duration, and analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
call_idYesThe unique identifier of the call to retrieve

Implementation Reference

  • Handler logic for the retell_get_call tool. Makes a GET request to the Retell API endpoint `/v2/get-call/{call_id}` using the provided call_id argument.
    case "retell_get_call":
      return retellRequest(`/v2/get-call/${args.call_id}`, "GET");
  • Input schema definition for the retell_get_call tool, specifying that a 'call_id' string parameter is required.
    {
      name: "retell_get_call",
      description: "Retrieve details of a specific call including transcript, recording URL, duration, and analysis.",
      inputSchema: {
        type: "object",
        properties: {
          call_id: {
            type: "string",
            description: "The unique identifier of the call to retrieve"
          }
        },
        required: ["call_id"]
      }
    },
  • src/index.ts:1283-1285 (registration)
    Registration of the tool list handler, which returns the array of tools including the schema for retell_get_call.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
  • src/index.ts:1287-1313 (registration)
    Registration of the tool execution handler, which dispatches to executeTool based on the tool name 'retell_get_call'.
    // Register tool execution handler
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const { name, arguments: args } = request.params;
    
      try {
        const result = await executeTool(name, args as Record<string, unknown>);
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : String(error);
        return {
          content: [
            {
              type: "text",
              text: `Error: ${errorMessage}`,
            },
          ],
          isError: true,
        };
      }
    });
  • Helper function used by the retell_get_call handler to make authenticated HTTP requests to the Retell AI 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?

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a retrieval operation but doesn't mention authentication requirements, rate limits, error conditions, or what happens if the call_id doesn't exist. It lists data elements returned but doesn't describe format, completeness, or access permissions for recordings.

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, efficient sentence that front-loads the core purpose ('retrieve details of a specific call') followed by specific data elements. Every word contributes value with zero waste or redundancy.

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?

For a read operation with 100% schema coverage and no output schema, the description adequately covers what data is retrieved. However, without annotations and with behavioral gaps (no error handling, authentication, or format details), it's minimally complete but leaves important operational context unspecified.

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?

Schema description coverage is 100% with the single parameter 'call_id' well-documented in the schema. The description doesn't add any parameter-specific information beyond what the schema provides (e.g., format examples, where to find call IDs, or validation rules), so it meets the baseline for high schema coverage.

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

Purpose4/5

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

The description clearly states the tool's purpose: 'Retrieve details of a specific call' with specific data elements listed (transcript, recording URL, duration, analysis). It uses a specific verb ('retrieve') and resource ('call'), but doesn't explicitly distinguish it from sibling tools like 'retell_get_agent' or 'retell_get_chat' which retrieve different resources.

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

Usage Guidelines2/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 versus alternatives. It doesn't mention sibling tools like 'retell_list_calls' (for listing multiple calls) or 'retell_update_call' (for modifying calls), nor does it specify prerequisites or appropriate contexts for retrieval.

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