Skip to main content
Glama

campaign

Destructive

Control LinkedIn outreach lifecycle: launch, pause, resume, archive, delete, or emergency-stop runs, and retry failed work or repair queues.

Instructions

Launch, pause, resume, archive, delete or emergency-stop a campaign.

Every action here changes what happens next. Watching one run, or reading
its history, is campaign_status.

Args:
    action: "launch", "pause", "resume", "archive", "delete",
        "emergency_stop", "retry_failed", "repair_queue" or
        "clear_coordinator_hold".
    campaign_id: Which campaign. Uses the active one if empty.
    confirm: Required by the actions that destroy work.
    icp_hold_ok: launch and resume only: True after the user chose "launch
        anyway" on a target the ICP research agent held.

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>"
    },
    "name": "campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
confirmNo
campaign_idNo
icp_hold_okNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.10.501
    • addedInput schema / properties / icp_hold_ok
      Added value: +{
      +  "default": false,
      +  "title": "Icp Hold Ok",
      +  "type": "boolean"
      +}
  2. First observedv0.10.375

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is known; the description adds real value on top by tying 'confirm' to the actions that destroy work and by explaining the icp_hold_ok override flow after an ICP hold. It does not specify which of the nine actions actually require confirm, nor whether delete/archive are reversible.

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?

The routing sentence is front-loaded and the highest-value fact (this mutates state) leads. The docstring-style 'Args:' block is somewhat mechanical but every line carries information an agent needs; nothing is redundant filler.

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 four-parameter destructive action-dispatcher with no output schema, the description covers the action space, the confirmation gate, the campaign targeting default, and the ICP-hold override. It leaves the post-action return shape and the exact confirm-required action list implicit, which are the remaining gaps.

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 description coverage is 0% and the action parameter has no enum, so the description carries the full burden — and it does: it enumerates all nine action strings, explains that an empty campaign_id falls back to the active campaign, flags confirm as required for destructive actions, and defines icp_hold_ok's 'launch anyway' meaning. The only gap is that 'the actions that destroy work' is not mapped to specific action names.

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 opening line names a specific resource (campaign) and an explicit set of verbs (launch, pause, resume, archive, delete, emergency-stop), and then names the sibling it is not: 'Watching one run, or reading its history, is campaign_status.' An agent can distinguish this mutation tool from the read-only status sibling without opening either schema.

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 a clear when-to-use rule ('Every action here changes what happens next') and routes monitoring/history to campaign_status, plus conditions on individual parameters (confirm for destructive actions, icp_hold_ok only for launch/resume). It stops short of mentioning create_campaign or edit_campaign as the alternatives for creating/changing campaign definitions, so the sibling routing is not exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.