Skip to main content
Glama

retell_delete_conversation_flow

Remove a conversation flow from the Retell AI platform by specifying its ID to manage agent configurations.

Instructions

Delete a conversation flow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
conversation_flow_idYesThe conversation flow ID to delete

Implementation Reference

  • The handler for the retell_delete_conversation_flow tool. It calls the generic retellRequest helper to perform a DELETE request to the Retell API endpoint /delete-conversation-flow/{conversation_flow_id}.
    case "retell_delete_conversation_flow":
      return retellRequest(`/delete-conversation-flow/${args.conversation_flow_id}`, "DELETE");
  • The input schema defining the required conversation_flow_id parameter for the tool.
    inputSchema: {
      type: "object",
      properties: {
        conversation_flow_id: {
          type: "string",
          description: "The conversation flow ID to delete"
        }
      },
      required: ["conversation_flow_id"]
    }
  • src/index.ts:874-887 (registration)
    The tool registration object added to the tools array, which is used by the MCP server for listing available tools.
    {
      name: "retell_delete_conversation_flow",
      description: "Delete a conversation flow.",
      inputSchema: {
        type: "object",
        properties: {
          conversation_flow_id: {
            type: "string",
            description: "The conversation flow ID to delete"
          }
        },
        required: ["conversation_flow_id"]
      }
    },
  • Generic helper function that performs authenticated HTTP requests to the Retell API, used by all tool handlers including this one.
    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 for behavioral disclosure. It states the tool deletes a conversation flow, implying a destructive operation, but doesn't specify if deletion is permanent, requires specific permissions, has side effects (e.g., affecting related calls or chats), or provides confirmation. This leaves significant behavioral gaps 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 with zero waste. It's appropriately sized for a simple deletion tool and front-loads the core action, making it easy to parse quickly.

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?

Given the tool's destructive nature, lack of annotations, and no output schema, the description is incomplete. It doesn't address critical context like deletion consequences, error handling, or return values, which are essential for safe agent operation. Sibling tools provide more context (e.g., retell_delete_call has similar gaps), but this doesn't compensate for the missing information.

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?

The input schema has 100% description coverage, with the parameter 'conversation_flow_id' clearly documented. The description doesn't add any meaning beyond the schema (e.g., format examples or sourcing guidance), so it meets the baseline of 3 where the schema does the heavy lifting.

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

Purpose3/5

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

The description states the action ('Delete') and target resource ('a conversation flow'), which provides basic purpose clarity. However, it doesn't specify what a conversation flow is or how it differs from other conversation-related resources like calls or chats, making it somewhat vague compared to sibling tools like retell_delete_call or retell_delete_chat_agent.

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 about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing an existing conversation flow), exclusions, or relationships to sibling tools like retell_list_conversation_flows or retell_update_conversation_flow, leaving the agent with no usage context.

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