Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Update campaign

update_campaign
Idempotent

Change an existing campaign's name, targeting, signals, offering, messaging, objective, review mode, scoring, AI email, or webhook settings while leaving omitted fields unchanged.

Instructions

Changes a campaign's name, targeting, signals, offering, objective or messaging, or its review_mode, min_score, ai_first_email and webhook_url; fields left out stay as they are. signals replaces the whole set, and saved signals come back in signal_items as the searches they become (one per source, each with a summary line). Returns research_options (review_mode, min_score) and waiting_review (how many prospects wait for approval). A 400 error carries a plain reason; 404 means the campaign is unknown or archived. Returns the campaign with view_in_producerspark. Saves only; nothing is searched, sent or charged.

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": "update_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
signalsNo
offeringNo
messagingNo
min_scoreNoFit (0 to 1) plus intent (0 to 3) a prospect needs before enrollment; 0 switches it off. Anyone below it stays on the list but is not enrolled.
objectiveNo
targetingNo
campaign_idYes
review_modeNoTrue: each researched prospect waits on the Golden List until approved with review_prospect before any outreach. False: enrollment needs no approval (the default).
webhook_urlNoAn https address that receives signed JSON events (prospect.researched, prospect.signal, prospect.added); the result's research_options.webhook_secret verifies the X-ProducerSpark-Signature header (sha256 HMAC of '<timestamp>.<body>'). Empty switches it off.
ai_first_emailNoTrue: for each prospect with a signal found, a whole first email is written from their evidence, the offering and the messaging instructions, and takes Email 1; everyone else gets Email 1 as authored. When false (the default), Email 1 stays as authored for everyone and the {{signal_line}} placeholder carries the per-person text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), the description discloses the non-obvious mutation shape: omitted fields are preserved, and signals is a full replacement rather than an append. It also covers error behavior (400 carries a plain reason, 404 means unknown or archived) and explicitly scopes side effects ("nothing is searched, sent or charged"), which an agent could not infer from the hints alone.

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 first sentence is dense but front-loads the field list and the preservation rule, and subsequent sentences move to returns and error codes in a logical order. "Returns the campaign with view_in_producerspark" is slightly redundant after the earlier returns sentence, but nothing is seriously wasteful.

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 11 parameters and no output schema, the description carries the return burden and does so: it names signal_items, research_options, waiting_review, and the error semantics. For a mutation tool of this complexity, an agent has enough to call it and interpret the response correctly.

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 coverage is only 36% across 11 parameters, so the description has to compensate, and it does by naming all ten optional fields and explaining the two semantics that matter most: partial update and whole-set replacement for signals. It stops short of restating per-field meaning (e.g. what min_score measures or what review_mode gates), which the schema already carries.

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?

The description opens with a specific verb and resource ("Changes a campaign's...") and enumerates the mutable fields, so the agent knows exactly what surface the tool covers. It hints at differentiation from per-signal siblings by stating "signals replaces the whole set," but never names an alternative tool outright.

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?

"Fields left out stay as they are" establishes partial-update semantics, and "Saves only; nothing is searched, sent or charged" implicitly separates this from activate/start-sending siblings. However, it never states when to choose this over update_campaign_signal, add_campaign_signal, or add_people_to_campaign, leaving the routing inference to the agent.

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