Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Create campaign

create_campaign
Idempotent

Saves a new campaign as a draft with required targeting and optional signals, offering, objective, and messaging; reuse an idempotency key to avoid duplicate drafts.

Instructions

Saves a new campaign as a draft, with its own Golden List. targeting (the prospects' industry and titles) is required; signals and offering are optional here and required before activation; objective and messaging are optional. The same idempotency_key returns the campaign already saved instead of creating another. A 400 error carries a plain reason. Returns the campaign with view_in_producerspark. Saves only; nothing is searched, sent or charged. To put people a find_people search found on it, call add_people_to_campaign next; naming them in targeting does not add them.

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": {
      "idempotency_key": "<idempotency_key>",
      "targeting": "<targeting>"
    },
    "name": "create_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
signalsNo
offeringNo
messagingNo
objectiveNo
targetingYesStep 1, the prospects' industry and titles: target industry, company size, titles and places, in the customer's words.
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, the description discloses idempotency behavior (same idempotency_key returns the existing campaign), error behavior (a 400 carries a plain reason), the return shape (the campaign with view_in_producerspark), and the side-effect boundary ("Saves only; nothing is searched, sent or charged"). These are exactly the traits an agent needs before invoking a write tool.

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?

It is front-loaded with the core action and packed with useful detail, but the semicolon-chained clauses and parentheticals make it denser than ideal. Nearly every sentence earns its place, so the length is defensible.

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 7-parameter write tool with no output schema, the definition covers required versus optional fields, activation prerequisites, idempotency, error signaling, return value, side effects, and the follow-up call. Nothing an agent needs to call it correctly is missing.

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?

With low schema description coverage, the description carries most of the load and does so well: it explains targeting's content (industry and titles), the staged role of signals and offering, the optional status of objective and messaging, and the idempotency_key semantics. The name parameter is not addressed in the description, a small gap the schema itself covers.

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 opening sentence gives a specific verb and resource ("Saves a new campaign as a draft, with its own Golden List") and the closing sentence distinguishes it from sibling tools by name (find_people, add_people_to_campaign). An agent can identify this tool without opening the 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?

It states what is required now (targeting), what is optional now but required before activation (signals, offering), and what is fully optional (objective, messaging). It also gives the explicit next step (call add_people_to_campaign) and the explicit exclusion (naming people in targeting does not add them).

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