Skip to main content
Glama

Text-Em-All MCP by usefulapi

by io.usefulapi
OverviewDiscussionsAdmin

Send a conversation text

send_text_message
Destructive

MUTATES Text-Em-All data AND SENDS A TEXT (spends credits): sends a 1:1 conversation text message immediately from one of your toll-free text numbers to a single contact. Text-Em-All API: POST /v1/conversations. You need a textNumberId (from list_text_numbers). Returns the conversation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoAdditional documented Text-Em-All fields to send verbatim in the JSON write body, using the API's PascalCase names (e.g. CallerID, TextNumberID, Lists, RetryTimes). Merged OVER the typed fields above.
messageYesThe text message body. Required.
lastNameNoRecipient last name (Contact.LastName).
firstNameNoRecipient first name (Contact.FirstName).
phoneNumberYesThe recipient's phone number (e.g. 9725551212). Required.
textNumberIdYesThe TextNumberID of the toll-free number to send from (see list_text_numbers). Required.
truncateIfExceedsLimitNoTruncate the message if it exceeds the length limit (TruncateIfExceedsLimit).

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 / textNumberId / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
    • addedInput schema / properties / textNumberId / type
      Added value: +[
+  "string",
+  "number"
+]
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The destructiveHint annotation signals mutation, but the description goes further and discloses the traits an agent cannot infer: it spends credits, sends immediately/unrecoverably, hits POST /v1/conversations, and returns the conversation. That is substantive context beyond the annotation.

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?

Front-loads the highest-signal warnings (MUTATES, sends, spends credits) before the mechanics. Dense, single-paragraph, with every clause earning its place.

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

Completeness5/5

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

With no output schema, the description still states the return value ('the conversation'), and it covers mutation, cost, endpoint, and the required id dependency. Nothing an agent needs to call this correctly is missing.

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%, so the schema already documents all 7 parameters, establishing a baseline of 3. The description adds the acquisition path for textNumberId (list_text_numbers) but no format or constraint detail beyond what the schema provides.

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 ('sends a 1:1 conversation text message'), and pins the scope tightly: immediate, toll-free number, single contact. This cleanly distinguishes it from the bulk-oriented sibling create_broadcast.

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?

Makes the when-to-use condition clear via '1:1 ... to a single contact' and 'immediately', implying it is not for bulk sends. It also routes the agent to list_text_numbers for the required id, though it never explicitly names create_broadcast as the bulk alternative.

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