Skip to main content
Glama

Twilio

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Twilio Get Message

twilio_get_message
Read-onlyIdempotent

Get details of a specific Twilio message by its SID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sidYesMessage SID (starts with SM...)
_authTokenYesTwilio Auth Token
_accountSidYesTwilio Account SID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoDestination phone number
sidNoMessage SID
uriNoAPI URI for this message
bodyNoMessage body text
fromNoSender phone number
priceNoMessage cost
statusNoMessage status
date_sentNoISO 8601 sent timestamp
error_codeNoError code if failed
price_unitNoCurrency unit
account_sidNoAccount SID
date_createdNoISO 8601 creation timestamp
date_updatedNoISO 8601 update timestamp
error_messageNoError message if failed

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "account_sid": {
+      "description": "Account SID",
+      "type": "string"
+    },
+    "body": {
+      "description": "Message body text",
+      "type": "string"
+    },
+    "date_created": {
+      "description": "ISO 8601 creation timestamp",
+      "type": "string"
+    },
+    "date_sent": {
+      "description": "ISO 8601 sent timestamp",
+      "type": "string"
+    },
+    "date_updated": {
+      "description": "ISO 8601 update timestamp",
+      "type": "string"
+    },
+    "error_code": {
+      "description": "Error code if failed",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "error_message": {
+      "description": "Error message if failed",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "from": {
+      "description": "Sender phone number",
+      "type": "string"
+    },
+    "price": {
+      "description": "Message cost",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "price_unit": {
+      "description": "Currency unit",
+      "type": "string"
+    },
+    "sid": {
+      "description": "Message SID",
+      "type": "string"
+    },
+    "status": {
+      "description": "Message status",
+      "type": "string"
+    },
+    "to": {
+      "description": "Destination phone number",
+      "type": "string"
+    },
+    "uri": {
+      "description": "API URI for this message",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_accountSid": "ACxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
+    "_authToken": "your-twilio-auth-token",
+    "sid": "SMxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
+  }
+]
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, effectively communicating safety. The description adds only that it 'gets details,' which is consistent but does not elaborate on authentication requirements or rate limits beyond the schema.

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?

The description is a single, concise sentence that directly states the tool's purpose. No extraneous information is included.

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?

For a simple read operation with complete annotations and an output schema (exists but not shown), the description is adequate. It could mention that authentication credentials are required, but those are already listed in the schema.

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 each parameter already described (e.g., sid: 'Message SID (starts with SM...)'). The description emphasizes the sid parameter but adds no new meaning beyond the schema.

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 'Get details of a specific Twilio message by its SID,' specifying the verb (Get), resource (Twilio message), and identifier (SID). This distinguishes it from siblings like twilio_list_messages or twilio_send_sms.

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 description implies usage when you have a message SID and need details. The presence of sibling twilio_list_messages provides context for when to use listing vs. single retrieval, but no explicit when-not-to-use or alternatives are given.

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