Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Update campaign signal

update_campaign_signal
Idempotent

Replaces one signal's wording by signal_key while keeping other campaign signals intact. Use it to revise a single research signal without rebuilding the campaign.

Instructions

Replaces the wording of one target signal (by its signal_key) and keeps the campaign's other signals. Returns the campaign with signal_items, including the changed signal's summary, and view_in_producerspark. On an active campaign, a changed signal makes every prospect due for research again (three first); nobody is charged twice for a person. 404 means the campaign or signal key is unknown.

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>",
      "signal_key": "<signal_key>",
      "text": "<text>"
    },
    "name": "update_campaign_signal"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesOne signal in the customer's words, verbatim; it becomes one search per source it can be checked from.
signal_keyYesThe key of one signal, from signal_items on list_campaigns or get_started.
campaign_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, and the description does not contradict them. It adds genuine context beyond the annotations, namely that on an active campaign changing a signal re-queues every prospect for research, that nobody is charged twice for a person, and that 404 signals an unknown campaign or key. The phrase 'three first' is garbled and blunts otherwise useful billing information.

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 definition is front-loaded with the action and scope, followed by return value, side effects, and error semantics in a compact block. Most sentences earn their place, though the garbled billing phrase 'three first' adds noise and one clause about view_in_producerspark is opaque without further explanation.

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?

With no output schema, the description does well to state the return shape, including signal_items and view_in_producerspark, and it covers the main error case. The remaining gap is that it does not clarify what a replaced signal's prior text becomes or whether the old search results are discarded, which matters for a text-replacement mutation with research side effects.

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 67%, and the schema already explains text and signal_key in detail. The description reinforces signal_key as the selector and adds behavioral meaning to text, namely the research re-queue, but it says nothing about campaign_id or about the maxLength and minLength constraints already covered by the schema.

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: 'Replaces the wording of one target signal (by its signal_key) and keeps the campaign's other signals.' That scope implicitly separates it from add_campaign_signal and delete_campaign_signal, though it never names those siblings, so the agent must infer the boundary rather than be told it directly.

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?

The usage context is implied rather than stated: replacing the wording of an existing signal, not adding or removing one. There is no explicit 'use this when / not when' guidance and no mention of its siblings as alternatives, so routing depends on the agent inferring intent from the scope sentence.

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