Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Pause campaign sending

pause_campaign_sending
Idempotent

Pause a campaign to stop all email and LinkedIn sending while preserving enrolled contacts and deleting nothing; resume later to continue from the same place.

Instructions

Stops a campaign's sending, email and LinkedIn steps both. Enrolled people keep their place until sending is switched back on. Nothing is sent or deleted. Returns the get_campaign_email shape.

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

Input Schema

NameRequiredDescriptionDefault
campaign_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare non-destructive, idempotent, non-read-only, closed-world behavior; the description goes beyond them by explaining that enrolled people retain their position, that nothing is sent or deleted, and that the operation is reversible. It also discloses the return shape ('get_campaign_email shape'), which matters because no output schema exists. It stops short of stating permission requirements or what happens if the campaign is already paused.

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 action and scope, then state effects, then the return value. Every sentence adds information an agent would otherwise have to guess at; there is no 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 one-parameter mutation tool with no output schema, the description covers what changes, what is preserved, reversibility, and the return shape, while annotations cover the safety profile. Minor gaps remain around authorization needs and the already-paused case, but nothing critical to correct invocation is missing.

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 0% and the single campaign_id parameter is never described in the text, so the only semantic lift comes from the possessive 'a campaign's sending,' which implies the id identifies the campaign. The parameter name is largely self-explanatory, but no format, constraint, or behavior for invalid ids is added.

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 description opens with a specific verb and resource ('Stops a campaign's sending') and immediately scopes it ('email and LinkedIn steps both'), which lets an agent separate it from delete-like or enrollment-changing siblings. It also distinguishes itself from a destructive alternative by stating 'Nothing is sent or deleted.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the reversibility clause ('until sending is switched back on') signals this is the non-destructive stop option, but there is no explicit when-to-use rule or named alternative such as start_campaign_sending. An agent can infer the intent, but must do the work itself.

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

Deploy Server

Other Tools