Skip to main content
Glama

release_twilio_number

Destructive

Release (delete) a Twilio SMS/voice number from the workspace. This does not remove WhatsApp Cloud API waNumbers. Pass the full request body for /utils/twilio/release-number as an object — typically includes phoneNumber or phoneNumberSid.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "payload": "<payload>"
    },
    "name": "release_twilio_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYesFull request body object for /utils/twilio/release-number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description still adds real context beyond that: it spells out 'Release (delete)' and explicitly excludes WhatsApp waNumbers, which the annotations cannot convey. It does not restate irreversibility or error behavior, but that is largely covered by idempotentHint=false.

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?

Two sentences, front-loaded with the action and scope, then the payload guidance. No filler or repeated information from annotations.

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?

No output schema is needed, and the destructive nature is annotated. However, this tool is a raw passthrough to an external endpoint whose contract ('/utils/twilio/release-number') an agent cannot inspect, and the description only says the payload 'typically includes' one of two keys without stating which is required or what else the body accepts. For an opaque nested-object request body that is a meaningful gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% but the schema only says 'Full request body object', which is meaningless on its own; the description compensates by naming the endpoint and giving typical keys (phoneNumber or phoneNumberSid). The word 'typically' leaves it ambiguous whether either key is required or what other keys are valid, keeping it below a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (release/delete a Twilio SMS/voice number) and immediately scopes it by excluding WhatsApp Cloud API waNumbers, which separates it from the WhatsApp and SMS number siblings. An agent can tell what this does and what it does not do without touching the schema.

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

Usage Guidelines4/5

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

The WhatsApp exclusion gives a clear condition for when this tool is not the right one, and the destructive framing signals deliberate use. It stops short of pointing to the actual alternative (sms_numbers_write / whatsapp_numbers_write) or stating prerequisites like verification that the number is in the workspace.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources