Skip to main content
Glama
AiAgency-Now

VoiceAI-MCP-VAVicky

Official
by AiAgency-Now
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

update_twilio_number

Modify Twilio phone number settings including friendly name, voice webhook, and SMS webhook URLs for custom VoiceAI integrations.

Instructions

Update Twilio number configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
number_sidYesNumber SID
friendly_nameNoFriendly name
voice_webhookNoVoice webhook URL
sms_webhookNoSMS webhook URL

Implementation Reference

  • index.js:638-645 (handler)
    Switch case in executeTool method implementing the tool logic: sets up a PATCH request to update Twilio number configuration via backend API.
    case 'update_twilio_number':
  url = `${this.baseUrl}/twilio/numbers/${args.number_sid}`;
  method = 'PATCH';
  body = {};
  if (args.friendly_name) body.name = args.friendly_name;
  if (args.voice_webhook) body.webhook = args.voice_webhook;
  if (args.sms_webhook) body.smsWebhook = args.sms_webhook;
  break;
  • index.js:371-380 (schema)
    Input schema definition for the update_twilio_number tool, specifying parameters and requirements.
    inputSchema: {
  type: 'object',
  properties: {
    number_sid: { type: 'string', description: 'Number SID' },
    friendly_name: { type: 'string', description: 'Friendly name' },
    voice_webhook: { type: 'string', description: 'Voice webhook URL' },
    sms_webhook: { type: 'string', description: 'SMS webhook URL' }
  },
  required: ['number_sid']
}
  • index.js:368-381 (registration)
    Tool object in the listTools response registering the update_twilio_number tool with its name, description, and schema.
    {
  name: 'update_twilio_number',
  description: 'Update Twilio number configuration',
  inputSchema: {
    type: 'object',
    properties: {
      number_sid: { type: 'string', description: 'Number SID' },
      friendly_name: { type: 'string', description: 'Friendly name' },
      voice_webhook: { type: 'string', description: 'Voice webhook URL' },
      sms_webhook: { type: 'string', description: 'SMS webhook URL' }
    },
    required: ['number_sid']
  }
},

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Update' implies a mutation operation, but the description doesn't specify required permissions, whether changes are reversible, rate limits, or what the response looks like. This is inadequate for a mutation tool with zero annotation coverage.

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 wasted words. It's appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration.

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 mutation tool with no annotations and no output schema, the description is incomplete. It lacks behavioral context (e.g., side effects, error handling) and doesn't compensate for the absence of structured data, making it insufficient for safe and effective use by an AI agent.

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 schema description coverage is 100%, with all parameters documented in the input schema. The description adds no additional meaning beyond the schema, such as explaining how parameters interact or providing examples. Baseline 3 is appropriate when the schema handles parameter documentation.

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') and resource ('Twilio number configuration'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from sibling tools like 'update_assistant' or 'update_smtp' beyond the resource type, missing explicit 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. It doesn't mention prerequisites (e.g., needing an existing Twilio number), exclusions, or comparisons to siblings like 'get_twilio_numbers' or 'buy_twilio_number', leaving usage context unclear.

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/AiAgency-Now/MCP-VoiceAI-WhiteLabel'

If you have feedback or need assistance with the MCP directory API, please join our Discord server