Skip to main content
Glama

Text-Em-All MCP by usefulapi

by io.usefulapi
OverviewDiscussionsAdmin

Send a broadcast

create_broadcast
Destructive

MUTATES Text-Em-All data AND SENDS MESSAGES (spends account credits): creates + sends a broadcast to the given contacts. Text-Em-All API: POST /v1/broadcasts. Set broadcastType to 'SMS' (a text broadcast — provide textMessage) or 'Announcement' (a voice broadcast — provide voiceText for text-to-speech, or a pre-recorded AudioID via fields.Audio). Contacts is a list of { primaryPhone, firstName?, lastName?, notes? }. Extra documented fields (CallerID, TextNumberID, Lists, RetryTimes, CallThrottle, MaxMessageLength, StartDate, CheckCallingWindow) go through fields (PascalCase). Returns the created broadcast.

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.
contactsYesRecipients (each needs primaryPhone). Required.
voiceTextNoText-to-speech message for an Announcement broadcast (mapped to Audio.TextToSpeech=true + Audio.Text).
textMessageNoThe text body for an SMS broadcast (TextMessage). Required when broadcastType='SMS'.
broadcastNameYesA name/label for this broadcast (BroadcastName). Required.
broadcastTypeYes'SMS' for a text broadcast, 'Announcement' for a voice broadcast. Required.
primaryPhoneNumbersOnlyNoOnly send to each contact's primary phone number (PrimaryPhoneNumbersOnly, default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The description goes well beyond the destructiveHint annotation, disclosing that it mutates data, sends real messages, and spends account credits, plus the return value. It stops short of covering auth requirements or rate limits, but the credit-spend warning is genuinely useful context.

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?

The most important warning — mutation and credit spend — is front-loaded in caps. The paragraph is dense but each sentence carries actionable information about types, fields, or contacts.

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?

Covers the mutation/credit implications, the endpoint, the SMS-vs-Announcement branching, contact structure, and the return value. With no output schema, stating 'Returns the created broadcast' fills the gap adequately.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real value by tying parameters together conditionally: textMessage is required for 'SMS' while voiceText or fields.Audio is needed for 'Announcement', and it clarifies the PascalCase passthrough convention for `fields`.

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 ('creates + sends a broadcast to the given contacts') and even names the API endpoint. It implicitly distinguishes itself from the sibling create_draft_broadcast by emphasizing that it actually sends, not just drafts.

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 — it mutates data and spends account credits — which tells an agent this is a real send operation, not a dry run. However, it never explicitly names create_draft_broadcast as the non-sending alternative or states when to prefer one over the other.

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