Skip to main content
Glama

twilio_list_calls

Lists calls from a connected Twilio account, newest first, with from, to, status, start/end times, and duration for reviewing recent call activity.

Instructions

(Beta) List the calls of a connected Twilio account, newest first: from, to, status, start and end, duratio...

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.446

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations and no output schema, the description carries the full burden, and it does disclose two real behavioral traits: results are ordered 'newest first' and each record carries from, to, status, start, end and duration. It stops there — no pagination, page-size, result caps, rate limits, or error behavior are described, and the text is cut off mid-word ('duratio...'), so the disclosure is partial rather than complete.

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?

The definition is a single front-loaded clause: beta marker, verb, resource, ordering, then the returned fields. Nothing is redundant, though the text terminates mid-word, leaving the field enumeration unfinished rather than deliberately trimmed.

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?

For a zero-parameter list tool with no output schema and no annotations, the description is the only source of truth about results, and it supplies ordering and a partial field list. It omits the things an agent still needs — pagination or result limits, whether filtering is possible at all given the empty schema, and the auth prerequisite — so it is adequate but incomplete.

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 tool takes zero parameters, so there is no parameter semantics to add and the baseline of 4 applies. The field list in the description describes the response shape rather than inputs, which is still useful but is not 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?

States a specific verb and resource ('List the calls of a connected Twilio account') plus ordering ('newest first'), which distinguishes it from single-record siblings like twilio_get_call. It never names a sibling or draws an explicit contrast, so it stops short of a 5.

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: nothing says when to list calls versus fetching a single call with twilio_get_call, nor when to prefer twilio_list_messages or twilio_api_request for filtered queries. The only contextual hint is the prerequisite 'connected Twilio account', which implies connect_twilio must run first, but that is inference rather than stated 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