Skip to main content
Glama

Text-Em-All MCP by usefulapi

by io.usefulapi
OverviewDiscussionsAdmin

List text numbers

list_text_numbers
Read-only

List the toll-free text (SMS) numbers on your account as a Feed. Each TextNumber has a TextNumberID you need to send a 1:1 conversation text (see send_text_message). Text-Em-All API: GET /v1/textnumbers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number (Feed `page`).
paramsNoAdditional documented equals-style query filters to send verbatim (e.g. BroadcastStatus=Completed). For range operators (Field~gte~value etc.) use the textemall_request escape hatch. Merged with paging above.
pagesizeNoNumber of items per page (Feed `pagesize`, default 10).
takesizeNoHow many items to return (Feed `takesize`; defaults to pagesize).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / properties / params / additionalProperties / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  }
-]
    • addedInput schema / properties / params / additionalProperties / type
      Added value: +[
+  "string",
+  "number",
+  "boolean"
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

readOnlyHint=true already covers safety, and the description adds that the result is returned as a Feed and that each entry carries a TextNumberID. That return-shape context matters because there is no output schema, though permissions, rate limits, and Feed traversal behavior are not mentioned.

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?

Three short sentences, front-loaded with the resource scope, then the practical reason for calling it, then the endpoint mapping. No restated or filler content.

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 read-only list tool with no output schema, the description supplies the essential return context (Feed of TextNumber objects, key field) and the endpoint. It stops short of describing what other TextNumber fields an agent can expect or how large feeds behave, which is a modest gap.

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 description coverage is 100%, so page, pagesize, takesize, and the params escape hatch are already documented in the schema. The description adds nothing about parameter behavior (defaults, paging interaction), so the baseline 3 applies.

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?

States a specific verb and resource ('List the toll-free text (SMS) numbers on your account as a Feed') and pins the API mapping with 'Text-Em-All API: GET /v1/textnumbers'. It also distinguishes itself from the action-oriented sibling by noting the returned TextNumberID is the input to send_text_message.

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?

Gives clear context for why an agent would call it: to obtain the TextNumberID required before sending a 1:1 conversation text. It does not, however, offer explicit when-not conditions or contrast with the other list_* siblings (list_broadcasts, list_lists).

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

All Text-Em-All MCP by usefulapi 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