Skip to main content
Glama

retell_delete_call

Remove a call and its associated data, including recordings and transcripts, from the Retell AI platform.

Instructions

Delete a call and all associated data including recordings and transcripts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
call_idYesThe unique identifier of the call to delete

Implementation Reference

  • Handler case in executeTool function that performs the DELETE request to Retell API endpoint /v2/delete-call/{call_id} using the generic retellRequest helper.
    case "retell_delete_call":
      return retellRequest(`/v2/delete-call/${args.call_id}`, "DELETE");
  • Tool definition including name, description, and input schema requiring 'call_id' parameter.
    {
      name: "retell_delete_call",
      description: "Delete a call and all associated data including recordings and transcripts.",
      inputSchema: {
        type: "object",
        properties: {
          call_id: {
            type: "string",
            description: "The unique identifier of the call to delete"
          }
        },
        required: ["call_id"]
      }
    },
  • src/index.ts:1283-1285 (registration)
    MCP server registration for listing all tools, which includes 'retell_delete_call' via the static 'tools' array.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
  • Generic HTTP request helper to Retell API with authentication, error handling, and JSON parsing, used by the tool handler.
    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();
    }
  • src/index.ts:1287-1313 (registration)
    MCP server handler for tool execution (CallToolRequestSchema), which dispatches to executeTool based on tool name.
    // 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,
        };
      }
    });
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool deletes a call and associated data, indicating a destructive operation, but lacks details on permissions required, whether deletion is reversible, error handling (e.g., if the call_id is invalid), or side effects (e.g., impact on linked resources). This is a significant gap for a mutation tool.

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 key action ('Delete') and scope. Every word earns its place by specifying the resource and what gets removed (recordings and transcripts), with no redundant or vague phrasing.

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

Completeness2/5

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

For a destructive tool with no annotations and no output schema, the description is incomplete. It lacks critical context such as confirmation of irreversibility, required permissions, error responses, or what happens to related entities. The high schema coverage doesn't compensate for these behavioral gaps, making it inadequate for safe agent use.

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' documented as 'The unique identifier of the call to delete'. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints. Baseline 3 is appropriate when the schema does the heavy lifting.

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 action ('Delete') and resource ('a call and all associated data including recordings and transcripts'), distinguishing it from siblings like retell_end_chat (which might terminate a chat without deletion) or retell_update_call (which modifies rather than removes). It specifies the comprehensive scope of deletion beyond just the call record.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., retell_end_chat for stopping a chat without deletion) or prerequisites (e.g., whether the call must be in a certain state). The description implies it's for permanent removal, but lacks explicit conditions or warnings about irreversible actions.

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