Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Delete campaign signal

delete_campaign_signal
DestructiveIdempotent

Remove a target signal by its signal_key and its Golden List filter from a campaign while keeping existing prospect research. Use it to clean up unwanted campaign signals; returns remaining signal items.

Instructions

Removes one target signal (by its signal_key) and its Golden List filter from a campaign. Research already done for it stays on the prospects. Returns the campaign with the remaining signal_items and view_in_producerspark. 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>"
    },
    "name": "delete_campaign_signal"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A4/5.0
Behavior4/5

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

With destructiveHint=true and idempotentHint=true already declared, the description adds real value: exactly what is destroyed (the signal and its Golden List filter), what is preserved (existing prospect research), the shape of the return (campaign with remaining signal_items and view_in_producerspark), and the 404 failure meaning. It stops short of stating permission requirements or any downstream effect on prospects already tagged by the signal.

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?

Three tight sentences, front-loaded with the destructive action, then what survives, then the return value and error semantics. Every sentence carries information; only the parenthetical '(by its signal_key)' mildly repeats what the schema states.

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?

For a two-parameter destructive mutation with no output schema, the description covers the action, the preserved side state, the return payload, and the error case, while annotations already declare destructiveness and idempotency. An agent has everything needed to call it and interpret the result.

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 50%: signal_key is already documented in the schema with provenance (signal_items from list_campaigns or get_started), and the description only echoes it as the identifier of the signal removed. campaign_id has no description in either place, so the definition does not compensate for the coverage gap; baseline 3 applies.

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 (removes), a precise resource (one target signal plus its Golden List filter), and the scoping unit (a campaign). It also draws a meaningful behavioral boundary that separates it from the add/update signal siblings by noting the research already done stays on prospects.

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 only implied by the verb 'removes'; there is no explicit statement of when to prefer this over update_campaign_signal (e.g., to clear a filter without dropping the signal) or any prerequisite warning. The note that research survives is helpful context, but it is scope clarification rather than when-to-use guidance.

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