Skip to main content
Glama

twilio_search_available_numbers

Search Twilio phone numbers available to buy in a country, including number, locality, region, and capabilities.

Instructions

(Beta) Search the phone numbers Twilio offers to buy in a country: number, locality, region and capabilities.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "twilio_search_available_numbers"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.446

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses beta status and enumerates what each result contains (number, locality, region, capabilities), which signals a non-mutating query, but it says nothing about result limits, pagination, or how country scoping is actually applied.

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?

A single front-loaded sentence: the beta marker, the action, and the returned fields all appear without filler. Nothing is wasted, though the trailing field list slightly blurs input versus output.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Because there is no output schema, the description sensibly lists the returned fields, so returns are covered. But the country-scoping statement is inconsistent with a zero-parameter schema, and no limits, pagination, or next-step guidance are given, leaving an agent unsure how the scope is determined.

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 has zero properties, which would normally be a baseline 4. However, the phrase 'in a country' strongly implies a country input that does not exist in the schema, creating ambiguity about whether the agent must supply one — a real defect for a no-parameter tool.

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?

It names a specific verb and resource: search the phone numbers Twilio offers to buy. The qualifier 'offers to buy' implicitly distinguishes this from listing numbers already owned (twilio_list_numbers) and from the purchase step (twilio_buy_number), though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'offers to buy' suggests this is the discovery step that precedes acquiring a number, but the description never states when to use this versus twilio_list_numbers or twilio_buy_number, nor does it give any exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools