Skip to main content
Glama

retell_delete_phone_number

Remove a phone number from your Retell AI account to release it from service, ensuring proper management of communication resources.

Instructions

Delete/release a phone number from your account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
phone_numberYesThe phone number in E.164 format to delete

Implementation Reference

  • The execution handler for the tool within the switch statement in executeTool function. It makes a DELETE request to the Retell API endpoint `/delete-phone-number/{phone_number}` using the helper retellRequest.
    case "retell_delete_phone_number":
      return retellRequest(`/delete-phone-number/${encodeURIComponent(args.phone_number as string)}`, "DELETE");
  • src/index.ts:388-400 (registration)
    The tool registration in the tools array, including name, description, and input schema. This array is returned by the ListTools handler to register all available tools.
      name: "retell_delete_phone_number",
      description: "Delete/release a phone number from your account.",
      inputSchema: {
        type: "object",
        properties: {
          phone_number: {
            type: "string",
            description: "The phone number in E.164 format to delete"
          }
        },
        required: ["phone_number"]
      }
    },
  • Input schema definition for the retell_delete_phone_number tool, specifying the required phone_number parameter.
      name: "retell_delete_phone_number",
      description: "Delete/release a phone number from your account.",
      inputSchema: {
        type: "object",
        properties: {
          phone_number: {
            type: "string",
            description: "The phone number in E.164 format to delete"
          }
        },
        required: ["phone_number"]
      }
    },
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 the action is 'Delete/release' but doesn't clarify if this is reversible, requires specific permissions, affects ongoing calls, or has rate limits. The dual terms 'Delete/release' add ambiguity about the exact behavior.

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 directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple deletion operation and front-loaded with the core action.

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 operation with no annotations and no output schema, the description is incomplete. It doesn't address critical context like whether deletion is permanent, what happens to associated resources, error conditions, or response format, leaving significant gaps for agent decision-making.

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 one parameter fully documented in the schema. The description adds no additional parameter semantics beyond what's in the schema (e.g., format details, validation rules, or examples), so it meets the baseline for high schema coverage without adding value.

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 action ('Delete/release') and resource ('a phone number from your account'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling deletion tools like 'retell_delete_agent' or 'retell_delete_call' beyond the resource type, which prevents a perfect score.

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 prerequisites (e.g., needing an existing phone number), consequences of deletion, or when to choose this over other deletion tools like 'retell_delete_phone_number' versus 'retell_import_phone_number' for managing numbers.

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