Skip to main content
Glama

Change many leads at once

dosai_bulk_leads
Destructive

One action over up to 200 leads (ids: dosai_list_leads): status (move them all to one status, a name from dosai_get_lead_statuses) or add_tag (add one tag of up to 40 characters to each; a lead that already has 20 tags is counted in failed). The owner's rules react to it as to a change made by hand: a rule "tag added: send a message" (dosai_list_rules) will write to EVERY client in the batch, so this tool needs the permission to write to clients and goes in two steps. Requires editor role.

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": {
      "project_id": "<project_id>",
      "action": "<action>",
      "lead_ids": "<lead_ids>",
      "value": "<value>"
    },
    "name": "dosai_bulk_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesThe status name, or the tag text (up to 40 characters).
actionYes
lead_idsYes
project_idYesFrom dosai_list_projects.
confirm_tokenNoLeave empty on the first call: it changes nothing and returns what will happen and a code. Ask the owner; only after their explicit "yes" call again with the same arguments and this code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  2. Changed2 schema fields changed
    • removedInput schema / properties / lead_ids / items / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already flag this as destructive, non-read-only, and open-world, so the safety profile is covered. The description adds genuinely useful context beyond them: owner rules fire as if the change were manual, batch-wide client messaging side effects, the 20-tag cap counting toward failed, and the two-step confirm pattern. However it does not describe the first-call preview payload or how partial failures are reported, leaving the return behavior undisclosed.

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?

Content is front-loaded with scope and actions first, then prerequisites, so an agent can act on the opening clause. The single dense paragraph with stacked parentheticals makes the side-effect warning easy to skim past, and splitting the confirmation rule into its own sentence would improve readability.

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

Completeness5/5

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

For a destructive bulk mutation with no output schema, the definition covers the limits (200 leads, 40-character tag, 20-tag cap), permissions, side effects on owner rules, and the confirmation protocol. Nothing essential for calling it safely and correctly is missing.

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 60%, and the description compensates by explaining what the value parameter means per action (status name vs tag text with the 40-character note) and by describing the confirm_token round trip. The add_tag overflow rule (a lead with 20 tags counts as failed) adds meaning the schema does not carry, though lead_ids and project_id receive no additional clarification.

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?

The description opens with a specific verb+scope ("One action over up to 200 leads") and enumerates the two supported operations, status and add_tag, with the value semantics of each. It points to dosai_list_leads, dosai_get_lead_statuses, and dosai_list_rules so an agent can distinguish this bulk-mutation tool from the single-lead and conversation-bulk siblings.

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?

It gives clear preconditions: editor role, permission to write to clients, and a mandatory two-step confirmation. It also names the companion tools for obtaining ids and valid status names, but it does not state when to prefer this over a single-lead update or explain exclusions against the sibling dosai_bulk_conversations.

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