Skip to main content
Glama

Bulk update contacts

bulk_update_contacts
Destructive

Add tags to, remove tags from, or delete many contacts by id.

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

Input Schema

NameRequiredDescriptionDefault
idsYesContact ids, up to 500
tagsNoRequired for add_tags and remove_tags
actionYesadd_tags and remove_tags take tags, delete removes the contacts

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / action / description
      Added value: +"add_tags and remove_tags take tags, delete removes the contacts"
    • addedInput schema / properties / ids / description
      Added value: +"Contact ids, up to 500"
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered. The description adds little beyond that: it does not say whether the delete is irreversible, whether partial failures leave some contacts updated, or how many operations can be chained. Useful but thin given this is an irreversible bulk mutation.

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?

A single front-loaded sentence that enumerates the three actions and the selector with zero filler. Nothing redundant or buried.

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?

There is no output schema, so the description would be the only place to say what a bulk run returns (per-id results, failure counts). For a destructive, non-idempotent batch operation that gap matters, and the description does not close 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 coverage is 100%, so the enum values, the 500-item cap and the 'tags required for add_tags/remove_tags' rule are all already documented. The description restates the action set but adds no new syntax or constraint detail. Baseline 3 is correct 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?

Specific verb set (add tags / remove tags / delete) against a clearly bounded resource ('many contacts by id'). The 'many'/'by id' phrasing implicitly separates it from the singular update_contact and delete_contact siblings, though it never names them.

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?

Bulk scope is implied by the title and 'many contacts', which suggests use over update_contact for multiple records, but there is no explicit when-to-use, when-not, or prerequisite statement. The choice of action is left entirely to the caller with no guidance on ordering or conflict handling.

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.