Skip to main content
Glama

Resume a lead

resume_campaign_lead
Destructive

Use this only when the user has asked to resume one stopped lead. Starts the lead's sequence again from where it stopped and queues its next message at once. A lead who unsubscribed, by an email's unsubscribe link or by asking in a reply, is refused with lead_unsubscribed: nothing is sent and the lead stays 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": {
      "campaignId": "<campaignId>",
      "leadId": "<leadId>"
    },
    "name": "resume_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

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the concrete side effect (queuing the next message at once), the failure path for unsubscribed leads with the specific error code lead_unsubscribed and the guarantee that nothing is sent, and that the call is free. This is exactly the kind of write-behavior context the destructiveHint/readOnlyHint flags cannot convey.

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 constraint, then effect, then refusal case, then cost. No sentence is redundant and the one-word 'Free.' earns its place as a billing signal.

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 tool with no output schema, the description covers the side effect, the error case, and cost. The one remaining gap is behavior when the lead is not in a stopped state or when the call is repeated, which matters given idempotentHint=false and an immediate queue action.

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%, and the schema already distinguishes leadId from personId with the correct id pattern. The description adds no further meaning about the two parameters, so the baseline 3 applies.

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?

States a specific verb and resource (resume a stopped lead) plus the exact effect: restarts the lead's sequence from where it stopped and queues the next message immediately. The scope is narrowed to a single lead, which separates it from campaign-level siblings such as pause_campaign or stop_campaign_lead.

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?

'Use this only when the user has asked to resume one stopped lead' gives an explicit trigger and an implicit exclusion of bulk or campaign-wide resume. It does not name an alternative tool for other resume scenarios, so it stops short of full routing guidance.

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