Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

twilio_list_messages

Read-onlyIdempotent

List SMS messages sent or received on a Twilio account, with optional filters for sender, recipient, and sent date to narrow results.

Instructions

List SMS messages sent or received on a Twilio account.

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": {
      "account_sid": "<account_sid>",
      "auth_token": "<auth_token>"
    },
    "name": "twilio_list_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
date_sentNoFilter by date (YYYY-MM-DD)
page_sizeNo
auth_tokenYes
account_sidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: no mention that account_sid and auth_token credentials are required, no pagination or page_size behavior, and no statement about result ordering or volume limits.

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?

A single front-loaded sentence with no waste. It is not padded, though it is arguably under-specified rather than efficiently scoped.

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

Completeness2/5

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

For a six-parameter tool requiring credentials, with no output schema and 17% schema coverage, the description should explain filtering, paging, and what is returned. None of that is present, leaving the agent to guess at page_size semantics and credential handling.

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

Parameters2/5

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

Schema coverage is only 17% — of six parameters only date_sent carries a schema description. The description says nothing about the to/from filters, page_size, or the required credential parameters, so it fails to compensate for the gap.

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 ('List') and resource ('SMS messages') plus the scope 'sent or received on a Twilio account'. It does not distinguish itself from twilio_get_message or twilio_list_calls, so the agent must infer the split from the names alone.

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?

No guidance on when to use this versus twilio_get_message (single message by SID) or twilio_list_calls. The 'sent or received' phrasing hints at a broad listing, but no exclusions, prerequisites, or alternatives are named.

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