Skip to main content
Glama

retell_update_phone_number

Modify phone number settings in Retell AI, including agent assignments for inbound and outbound calls, and update the nickname.

Instructions

Update settings for a phone number including assigned agents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
phone_numberYesThe phone number in E.164 format to update
inbound_agent_idNoNew agent ID for inbound calls (null to remove)
outbound_agent_idNoNew agent ID for outbound calls (null to remove)
nicknameNoNew nickname for the phone number

Implementation Reference

  • Handler implementation in the executeTool switch statement. Extracts phone_number from args, encodes it, and sends a PATCH request to Retell API endpoint `/update-phone-number/{phone_number}` with remaining update data.
    case "retell_update_phone_number": {
      const { phone_number, ...phoneUpdateData } = args;
      return retellRequest(`/update-phone-number/${encodeURIComponent(phone_number as string)}`, "PATCH", phoneUpdateData as Record<string, unknown>);
    }
  • Tool schema definition including name, description, and inputSchema with properties for phone_number (required), inbound_agent_id, outbound_agent_id, and nickname.
    name: "retell_update_phone_number",
    description: "Update settings for a phone number including assigned agents.",
    inputSchema: {
      type: "object",
      properties: {
        phone_number: {
          type: "string",
          description: "The phone number in E.164 format to update"
        },
        inbound_agent_id: {
          type: "string",
          description: "New agent ID for inbound calls (null to remove)"
        },
        outbound_agent_id: {
          type: "string",
          description: "New agent ID for outbound calls (null to remove)"
        },
        nickname: {
          type: "string",
          description: "New nickname for the phone number"
        }
      },
      required: ["phone_number"]
    }
  • src/index.ts:1283-1285 (registration)
    Registration of the ListToolsRequestHandler which returns the tools array containing this tool's schema.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
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. It states this is an update operation, implying mutation, but doesn't disclose behavioral traits like required permissions, whether changes are reversible, rate limits, or error handling. The description adds minimal context beyond the basic action, leaving significant 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core action and key fields. It avoids unnecessary words and gets straight to the point. However, it could be slightly more structured by explicitly listing updatable fields, but it's appropriately concise for the tool's complexity.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral aspects (e.g., side effects, permissions), usage context, and response format. While the schema covers parameters well, the overall context for safe and effective use is insufficient, especially for an update operation.

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%, so the schema already documents all parameters thoroughly. The description adds marginal value by mentioning 'assigned agents' (hinting at inbound_agent_id and outbound_agent_id) and 'settings' (implying nickname and other fields), but doesn't provide additional meaning beyond what's in the schema. Baseline 3 is appropriate as the schema does the heavy lifting.

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 ('Update settings') and resource ('phone number'), specifying what fields can be updated ('including assigned agents'). It distinguishes from sibling tools like retell_create_phone_number (create vs update) and retell_delete_phone_number (delete vs update), though it doesn't explicitly mention these distinctions. The purpose is specific but could be more precise about scope.

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 explicit guidance on when to use this tool versus alternatives is provided. The description implies usage for modifying phone number settings, but it doesn't mention prerequisites (e.g., phone number must exist), exclusions, or compare to tools like retell_update_agent for agent-specific changes. Usage is implied from the action, but no contextual advice is given.

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