Skip to main content
Glama

retell_delete_llm

Remove an LLM configuration from the Retell AI voice and chat agent platform to manage conversation flows and agent settings.

Instructions

Delete a Retell LLM configuration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
llm_idYesThe LLM configuration ID to delete

Implementation Reference

  • The execution handler for the retell_delete_llm tool within the executeTool function's switch statement. It constructs a DELETE request to the Retell API endpoint `/delete-retell-llm/{llm_id}` using the retellRequest helper.
    case "retell_delete_llm":
      return retellRequest(`/delete-retell-llm/${args.llm_id}`, "DELETE");
  • src/index.ts:788-800 (registration)
    Registration of the retell_delete_llm tool in the global tools array used for listing available tools via ListToolsRequestHandler.
    {
      name: "retell_delete_llm",
      description: "Delete a Retell LLM configuration.",
      inputSchema: {
        type: "object",
        properties: {
          llm_id: {
            type: "string",
            description: "The LLM configuration ID to delete"
          }
        },
        required: ["llm_id"]
      }
  • Input schema definition for the retell_delete_llm tool, specifying the required 'llm_id' parameter.
    inputSchema: {
      type: "object",
      properties: {
        llm_id: {
          type: "string",
          description: "The LLM configuration ID to delete"
        }
      },
      required: ["llm_id"]
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. 'Delete' implies a destructive mutation, but the description doesn't disclose whether deletion is permanent, requires specific permissions, has confirmation steps, or what happens to associated resources. This is a significant gap for a destructive operation.

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 states the core purpose without any fluff or redundant information. It's appropriately sized for a simple delete operation with one parameter.

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 mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain behavioral implications (permanence, side effects), success/failure responses, or usage context relative to sibling tools. The agent lacks critical information to use this tool safely and correctly.

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 'llm_id' fully documented in the schema. The description adds no additional parameter context beyond what's already in the structured schema, meeting the baseline expectation when schema coverage is complete.

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 verb ('Delete') and resource ('a Retell LLM configuration'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'retell_delete_agent' or 'retell_delete_knowledge_base', but the resource specificity (LLM configuration) provides implicit differentiation.

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, prerequisites, or consequences. With multiple delete operations available (agent, call, knowledge base, etc.), the agent receives no help in selecting the correct deletion tool for an LLM configuration specifically.

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