TwilioManager MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ADDRESS_CITY | No | City for address details (optional) | |
| ADDRESS_REGION | No | Region for address details (optional) | |
| ADDRESS_STREET | No | Street address details (optional) | |
| TWILIO_AUTH_TOKEN | Yes | Your Twilio authentication token | |
| TWILIO_ACCOUNT_SID | Yes | Your Twilio account SID | |
| ADDRESS_ISO_COUNTRY | No | ISO country code for address details (optional) | |
| ADDRESS_POSTAL_CODE | No | Postal code for address details (optional) | |
| ADDRESS_CUSTOMER_NAME | No | Customer name for address details (optional) | |
| ADDRESS_FRIENDLY_NAME | No | Friendly name for address details (optional) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_twilio_subaccountsB | List all Twilio subaccounts or filter by friendly name. Provide an empty string for all subaccounts |
| get_account_phone_numbersC | Get all phone numbers associated with a Twilio subaccount |
| get_all_phone_numbersC | Get all phone numbers associated with a Twilio subaccount |
| get_regulatory_bundle_sidC | Get the regulatory bundle SID for a Twilio subaccount |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Two tools have nearly identical purposes: 'get_account_phone_numbers' and 'get_all_phone_numbers' both retrieve phone numbers for Twilio subaccounts, creating clear ambiguity. The other two tools target distinct resources (regulatory bundles and subaccounts), but the overlap between the first two tools is significant and likely to cause misselection.
All tools follow a consistent verb_noun pattern (e.g., get_account_phone_numbers, list_twilio_subaccounts) with clear, descriptive names. The naming style is uniform across the set, making it easy to parse and understand the actions and targets.
With only 4 tools, the count feels thin for a server named 'TwilioManager MCP', which suggests broader Twilio API management. This limited set may not cover essential operations like sending messages, managing calls, or updating resources, making it borderline for the implied scope.
The tool surface is severely incomplete for Twilio management, lacking core functionalities such as sending SMS, making calls, or updating subaccounts. It focuses narrowly on retrieval operations (get/list) without create, update, or delete capabilities, leading to significant gaps that will hinder agent workflows.