Skip to main content
Glama

twilio_list_accounts

Lists Twilio accounts connected to Local MCP with Account SID, name, account type, and usage details so you can identify and select the right account.

Instructions

(Beta) List the Twilio accounts connected to LMCP: Account SID, name, type (Trial or Full), whether it uses...

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_list_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.446

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does add real value by naming the returned attributes and flagging the Beta status, and 'List' implies a non-mutating read. However, it discloses nothing about authentication, whether disconnected accounts appear, ordering, or the truncated final field — gaps that matter for a 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.

Conciseness3/5

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

The definition is short and the core scope is front-loaded before the field enumeration, which is good structure. But the text terminates mid-sentence ('...whether it uses...'), so it is under-specified rather than concise — a dangling clause that leaves the reader with an incomplete list of return fields.

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?

With no output schema, the description is the only place return values can be explained, and it does begin that job by naming Account SID, name, and type. The truncation means the return contract is only partially documented, and with no annotations nothing covers safety or side-effect expectations. Adequate as a starting point, but incomplete for a tool whose output shape is otherwise undocumented.

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?

The input schema has zero parameters, so there is nothing for the description to clarify and the baseline of 4 applies. No misleading parameter claims are made.

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 uses a specific verb and resource — 'List the Twilio accounts connected to LMCP' — and enumerates the fields returned (Account SID, name, type Trial/Full), which distinguishes it from sibling read tools like twilio_list_calls or twilio_list_numbers. The platform prefix plus the explicit field list makes the resource unambiguous. It falls short of a 5 only because the sentence is cut off mid-clause ('whether it uses...'), leaving the final described attribute unresolved.

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?

There is no when-to-use guidance, no statement of prerequisites (e.g. that an account must be connected first via connect_twilio), and no indication of when another tool is more appropriate. The only implicit signal is that it is a listing tool with no parameters, from which an agent can infer it returns everything connected. That is inference, not guidance.

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