Skip to main content
Glama

Bulk update numbers

bulk_update_numbers
Destructive

Act on many numbers at once: tag, untag, label, add to or remove from a pool, or release. Releasing cannot be undone.

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": {
      "ids": "<ids>",
      "action": "<action>"
    },
    "name": "bulk_update_numbers"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesNumbers to act on, in E.164
tagsNoadd_tags / remove_tags. Lowercased; up to 20 per number.
labelNoset_label; null clears
actionYesadd_to_pool and remove_from_pool take pool_id, add_tags and remove_tags take tags, set_label takes label, release takes confirm
confirmNorelease only
pool_idNoadd_to_pool / remove_from_pool

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / action / description
      Added value: +"add_to_pool and remove_from_pool take pool_id, add_tags and remove_tags take tags, set_label takes label, release takes confirm"
    • addedInput schema / properties / ids / description
      Added value: +"Numbers to act on, in E.164"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description still adds value by naming exactly which action is irreversible ('Releasing cannot be undone'), which annotations alone cannot pinpoint. It does not address partial-failure behavior on large batches or the confirm requirement, leaving some behavioral gaps.

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?

Two sentences, nothing wasted. The operation list comes first and the single safety caveat is placed at the end where it reads as a warning rather than buried 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?

With six parameters, a fully documented schema, and no output schema, the description covers the action space adequately. However, it never indicates what a bulk call returns or what happens when some of up to 1000 IDs fail, which is material for a destructive non-idempotent batch tool.

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 per-action parameter routing and the 1000-item cap, so the schema carries the semantics. The description's action list largely restates the enum ('tag, untag, label, add to or remove from a pool, or release') without adding format or constraint detail. Baseline 3 applies when the schema does the heavy lifting.

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 states a specific verb+resource ('Act on many numbers at once') and enumerates the six supported operations, which maps cleanly onto the action enum. It distinguishes itself from singular siblings like release_number and update_number_pool via 'many numbers at once', though it never names 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?

The bulk-vs-single scope is implied rather than stated as guidance, and there is no mention of when to prefer this over release_number, assign_number_to_customer, or bulk_update_contacts. An agent can infer the use case but must reason about the boundary itself.

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.