Skip to main content
Glama
TopSMS MCP server

TopSMS MCP server

get_bulk_job

Retrieve the progress of a queued bulk SMS send by job ID, including status, sent, failed, and queued counts plus optional per-message results.

Instructions

Get progress of a queued bulk send (status, sent, failed, queued counts and per-message results).

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": {
      "jobId": "<jobId>"
    },
    "name": "get_bulk_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesjobId returned by send_bulk_sms.
resultsNoInclude per-message results (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does usefully disclose what comes back (counts plus optional per-message results), which is behavioral value, but it says nothing about job lifecycle (are results retained after completion?), access requirements, or whether the call is side-effect free.

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 wasted words, and the returned-field parenthetical is genuinely informative rather than filler. It is dense but readable, and nothing could be removed without losing 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 two-parameter read tool with no output schema, describing the return payload inline is exactly the right compensation, and it does so. The remaining gap is polling/lifecycle guidance, which is minor for a simple status getter.

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 both jobId and results are already documented, including the default of true for results. The description's mention of 'per-message results' reinforces the results flag but adds no format or syntax detail beyond the schema; baseline 3 applies.

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 and resource — 'Get progress of a queued bulk send' — and enumerates the returned fields (status, sent, failed, queued counts). This clearly distinguishes it from send_bulk_sms (which creates the job) and get_message_status (single message), though it does not name those alternatives explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 'queued bulk send' and the jobId param tied to send_bulk_sms, so an agent can infer this is the polling tool for a bulk job. There is no explicit when-to-use statement, no mention of how often to poll, and no guidance on when to prefer get_message_status for individual messages.

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