Skip to main content
Glama

Add or Update Subscribers

add_subscribers
Destructive

Add or update subscribers in Mobile Text Alerts (bulk operation)

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": {
      "subscribers": "<subscribers>"
    },
    "name": "add_subscribers"
  }
}

Input Schema

NameRequiredDescriptionDefault
createOnlyNoWhen true, only create new subscribers and skip existing ones. When false, create new or update existing subscribers.
subscribersYesArray of subscribers to add/update (max 1000)

Output Schema

NameRequiredDescriptionDefault
dataYesRaw Mobile Text Alerts API response envelope, nested under `data.data`. IMPORTANT: partial failures are reported here, not via HTTP status — a call can return success with `errorRecordCount` above zero, so check `data.data.errorRecordCount` and `data.data.errorRecords` even when `success` is true.
errorNo
statusYes
contextNoAdditional context about why the call was blocked
successYes
errorCodeNoMachine-readable error code. 'ONBOARDING_REQUIRED' means the account has not finished brand registration. 'NO_SENDING_NUMBER' means no number on the account can send yet; 'SENDING_NUMBER_NOT_FOUND' / 'SENDING_NUMBER_UNAVAILABLE' mean the requested `from` number is not on the account or can't send. 'AUTH_FAILED', 'RATE_LIMITED', 'UPSTREAM_ERROR' and 'UPSTREAM_UNAVAILABLE' are Mobile Text Alerts API failures.
nextStepsNoExplicit recovery guidance for the calling agent
statusTextYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, and the description's 'add or update' wording usefully confirms upsert semantics, meaning existing records can be overwritten. It says nothing about partial-failure behavior on a 1000-item batch, what fields get overwritten, or rate limits, which is the kind of context a destructive bulk mutation would benefit from.

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 short sentence with no wasted words, and the core action is front-loaded. It is arguably too terse rather than padded, so the efficiency is real but comes at the cost of detail.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and only two parameters exist with full schema coverage. However, for a destructive bulk upsert the description leaves out operational expectations (overwrite scope, batch failure handling) that an agent would want before calling it.

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%, including the createOnly upsert switch and per-field subscriber properties, so the schema carries the parameter burden. The description adds only the notion of batching, not any syntax or format detail beyond the schema.

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?

The description gives a specific verb pair (add or update) plus the resource (subscribers) and the product (Mobile Text Alerts), and flags it as a bulk operation. That is enough to distinguish it from siblings like create_group or send_message, though it does not explicitly name any alternative.

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?

The only usage signal is the parenthetical 'bulk operation', which implies it should be used for many subscribers rather than one. There is no statement of when to prefer this over other tools, no prerequisites, and no exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources