Skip to main content
Glama

Campaign status

crm_set_campaign_status
Destructive

Pause, resume or conclude a campaign. Pausing and concluding require a reason — a goal someone stops pursuing is a decision that gets asked about later (CRM-7 extended). Concluded is terminal: the accounts stay fully readable (CRM-6), but the campaign takes no new targets. Effects: campaign.status moved, reason kept.

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": {
      "campaign_id": "<campaign_id>",
      "status": "<status>"
    },
    "name": "crm_set_campaign_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoRequired for paused and concluded.
statusYesWhere it moves.
campaign_idYesThe campaign. An existing campaign id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 explaining that concluded is terminal yet accounts remain fully readable, that no new targets are taken, and that the reason is persisted alongside the status. The destructiveHint=true annotation is consistent with a status move that blocks new targets, and the description clarifies the exact blast radius rather than repeating the annotation.

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?

Front-loaded with the action set, then prerequisites, then effects in a clear order with no filler. The internal references (CRM-7 extended, CRM-6) add some jargon the agent cannot resolve, which slightly blunts clarity.

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?

With no output schema, the description supplies what the call changes ('Effects: campaign.status moved, reason kept') plus preconditions and terminality, which is everything needed to invoke it correctly. A mutation tool with destructiveHint is adequately covered.

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%, so all three parameters are already documented in the schema, including the enum and the reason-required rule. The description adds only the 'reason kept' persistence detail, so baseline 3 is appropriate.

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 set (pause, resume, conclude) applied to a clear resource (campaign), and the three actions map directly to the status enum values. An agent can tell this apart from crm_update_campaign or crm_set_account_status because the scope is explicitly the campaign's lifecycle status.

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?

Gives clear conditional guidance: pausing and concluding require a reason, and concluded is terminal so the campaign takes no new targets. It does not name an alternative tool for other edits (e.g., renaming via crm_update_campaign), but the when-to-use context is well defined.

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.