Skip to main content
Glama

Stop a lead

stop_campaign_lead
DestructiveIdempotent

Use this when the user wants one person to receive nothing more from one campaign. Stops that lead's sequence there; other campaigns are not affected. Stopping a stopped lead changes nothing. 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": {
      "campaignId": "<campaignId>",
      "leadId": "<leadId>"
    },
    "name": "stop_campaign_lead"
  }
}

Input Schema

NameRequiredDescriptionDefault
leadIdYesThe lead's `id`, as the campaign's leads list gives it, not its `personId`.
campaignIdYesThe campaign's id.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the description's idempotency restatement ('Stopping a stopped lead changes nothing') adds little. It does add genuine context the annotations lack: the blast radius is limited to a single campaign, and the call is 'Free' (no cost/quota). It says nothing about what the response contains.

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?

Three short sentences, front-loaded with the usage trigger, then scope, then the idempotency note. Very little waste, though 'Free.' is terse to the point of ambiguity without surrounding context.

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-required-parameter mutation with rich annotations and no output schema, the description covers trigger, scope, idempotent behavior and cost. Missing only the response shape and what happens if the lead isn't in the campaign.

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% and both parameters are fully documented, including the leadId-vs-personId distinction, so the schema does the heavy lifting. The description adds no parameter-level 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 ('Stops that lead's sequence') and scopes it to one campaign, plus clarifies 'other campaigns are not affected.' It doesn't name stop_person_in_campaigns or resume_campaign_lead, so the differentiation is implied by scope 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: 'Use this when the user wants one person to receive nothing more from one campaign.' The scope restriction and the no-op note set clear boundaries, though no alternative tool is named for the cross-campaign or resume cases.

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