Skip to main content
Glama

Stop a person in campaigns

stop_person_in_campaigns
DestructiveIdempotent

Use this when one person should receive nothing more from several campaigns at once, such as after they replied elsewhere. Stops the person's sequence in 1 to 50 named campaigns. If one of the campaigns is unknown, or the person is in none of them, nothing is stopped. Free.

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": {
      "personId": "<personId>",
      "campaignIds": "<campaignIds>"
    },
    "name": "stop_person_in_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault
personIdYesThe person's id: a lead's `personId`, not its `id`.
campaignIdsYes1 to 50 campaigns to stop the person in, each once.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint, idempotentHint, and closed-world scope, so the description's job is additive. It does that well by disclosing all-or-nothing behavior ('If one of the campaigns is unknown, or the person is in none of them, nothing is stopped') and cost ('Free'), which are not derivable from the annotations or schema.

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?

Four short sentences, front-loaded with the usage condition, then scope, atomicity, and cost in descending priority. Nothing is redundant with the title, and even the one-word 'Free.' carries decision-relevant information.

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 mutation with full annotations and no output schema, the definition covers when to use it, the numeric limit, and the failure mode. It stops short of saying what a successful call returns (e.g., whether per-campaign results come back), which an agent might want given the partial-failure rule.

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 personId (lead's personId, not id) and campaignIds (1-50, unique) are already fully documented. The description only restates the count bound and adds no format or selection detail beyond the schema, making 3 the correct baseline.

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 ('Stops') and scoped resource ('the person's sequence in 1 to 50 named campaigns'), which lets an agent distinguish it from a single-campaign stop. It never names the singular sibling, so the differentiation is inferential rather than explicit.

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?

Opens with an explicit trigger condition ('when one person should receive nothing more from several campaigns at once') plus a concrete example scenario ('after they replied elsewhere'). No when-not conditions or named alternatives are given, keeping it below the top band.

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