Skip to main content
Glama

Twilio

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Twilio List Calls

twilio_list_calls
Read-onlyIdempotent

List recent phone calls from your Twilio account. Returns call SID, status, duration, and direction.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax calls to return (default 20, max 100)
_authTokenYesTwilio Auth Token
_accountSidYesTwilio Account SID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoEnd index
uriNoAPI URI for this resource
pageNoCurrent page number
callsNoArray of call objects
startNoStart index
totalNoTotal number of calls
page_sizeNoPage size
next_page_uriNoURI for next page
first_page_uriNoURI for first page
previous_page_uriNoURI for previous page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "calls": {
+      "description": "Array of call objects",
+      "items": {
+        "properties": {
+          "account_sid": {
+            "description": "Account SID",
+            "type": "string"
+          },
+          "date_created": {
+            "description": "ISO 8601 creation timestamp",
+            "type": "string"
+          },
+          "date_updated": {
+            "description": "ISO 8601 update timestamp",
+            "type": "string"
+          },
+          "direction": {
+            "description": "Call direction (inbound or outbound)",
+            "type": "string"
+          },
+          "duration": {
+            "description": "Call duration in seconds",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "end_time": {
+            "description": "ISO 8601 end timestamp",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "from": {
+            "description": "Caller phone number",
+            "type": "string"
+          },
+          "price": {
+            "description": "Call cost",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "price_unit": {
+            "description": "Currency unit",
+            "type": "string"
+          },
+          "sid": {
+            "description": "Call SID",
+            "type": "string"
+          },
+          "status": {
+            "description": "Call status (queued, ringing, in-progress, completed, etc.)",
+            "type": "string"
+          },
+          "to": {
+            "description": "Destination phone number",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "end": {
+      "description": "End index",
+      "type": "integer"
+    },
+    "first_page_uri": {
+      "description": "URI for first page",
+      "type": "string"
+    },
+    "next_page_uri": {
+      "description": "URI for next page",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "page": {
+      "description": "Current page number",
+      "type": "integer"
+    },
+    "page_size": {
+      "description": "Page size",
+      "type": "integer"
+    },
+    "previous_page_uri": {
+      "description": "URI for previous page",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "start": {
+      "description": "Start index",
+      "type": "integer"
+    },
+    "total": {
+      "description": "Total number of calls",
+      "type": "integer"
+    },
+    "uri": {
+      "description": "API URI for this resource",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_accountSid": "ACxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
+    "_authToken": "your-twilio-auth-token"
+  },
+  {
+    "_accountSid": "ACxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
+    "_authToken": "your-twilio-auth-token",
+    "limit": 50
+  }
+]
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations provide readOnlyHint, idempotentHint, destructiveHint. Description adds that calls are 'recent' and returns fields. No additional behavioral traits like pagination, sorting, or region-specific issues disclosed. Description is consistent with annotations.

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 efficient sentences, zero waste, front-loaded with purpose and key output info.

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

Completeness4/5

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

With high schema coverage and an output schema present, the description is fairly complete. It covers the basic return fields and purpose, though it could mention pagination or sorting constraints for a more thorough specification.

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?

Schema coverage is 100% with detailed parameter descriptions. The description does not add extra meaning beyond the schema for parameters; it only summarizes output fields. Baseline of 3 is appropriate.

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?

The description clearly states the verb 'list' and resource 'recent phone calls' and lists returned fields (call SID, status, duration, direction). This distinguishes it from siblings like twilio_make_call and twilio_list_messages.

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?

Implicit usage is clear for listing calls, but no explicit guidance on when to use this tool versus alternatives (e.g., twilio_get_message) or any preconditions. No 'when not to use' stated.

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

All Twilio toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources