Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Add people to campaign

add_people_to_campaign
Idempotent

Adds people found by a search to a campaign's Golden List, skipping contacts without a business email and saving only—no enrollment or sending.

Instructions

Puts the people a search found on a campaign's Golden List, the way Contacts does in the app. Works on a draft or an active campaign. People without a business email are skipped and counted in without_email; anyone already on the list stays as they are, and someone the owner removed comes back. Returns added, already_on_list and without_email. A name the search did not return is a 400 that names it, and nothing is added. Saves only: nothing is enrolled or sent. An active campaign starts its signal research on the new people; enroll_campaign_people puts them in the sequence.

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

Input Schema

NameRequiredDescriptionDefault
namesNoThe people from the search to add, by full name as the search returned it. Omitted: everyone it found.
goal_idYesThe goal_id of a finished find_people (or other people) search.
campaign_idYes
exclude_namesNoPeople from the search to leave out, by full name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the annotations: it discloses skip logic (people without a business email go to without_email), merge semantics for existing entries, restoration of owner-removed people, and a side effect on active campaigns (signal research starts). Annotations already cover safety/idempotency, so this adds the substantive behavior an agent cannot infer. It stops short of noting scale/rate limits for the 1000-name cap.

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-loads the core action and side-effect constraint, and every sentence carries distinct information (returns, errors, atomicity, alternatives). The prose is dense and somewhat run-on, which slightly raises parsing cost, but there is no filler.

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 the return fields (added, already_on_list, without_email), the failure mode (400 naming the offending name, nothing added), and the mutation scope. For a 4-parameter mutation tool that is enough for an agent to call it correctly and predict 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 75% and already documents names, exclude_names and goal_id, so the description has little room to add meaning. It reinforces the search-scoped nature of goal_id and the all-by-default behavior of names, plus the 400 on an unknown name, but adds no syntax or format detail beyond the schema. Baseline 3 for high coverage 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?

Names a specific verb and resource ('Puts the people a search found on a campaign's Golden List') and scopes it to the result set of a prior search. It also explicitly contrasts the outcome with enroll_campaign_people ('puts them in the sequence'), so an agent can separate the two without reading either schema.

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

Usage Guidelines5/5

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

States eligibility ('Works on a draft or an active campaign'), the key exclusion ('Saves only: nothing is enrolled or sent'), and the alternative for sequencing ('enroll_campaign_people puts them in the sequence'). That is an explicit when/when-not/alternative set.

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