Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

List campaigns

list_campaigns
Read-onlyIdempotent

Retrieve all campaigns for an account, including targeting, signals, offering, status, results, and signal research counts. Read-only.

Instructions

The account's campaigns. Each has its three steps (targeting: the prospects' industry and titles; signals: target signals in the customer's words, with signal_items splitting them one per entry; offering: what they offer), optional objective and messaging, name, status (draft, active or paused), is_default, its Golden List, results (prospects, signals, messages prepared) and signal research counts (ready, no_signal, queued, running, held, failed, pending), and view_in_producerspark. Reads only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so 'Reads only' is redundant. However, with no output schema the description does real work by disclosing the exact response shape per campaign — steps, status enum values, counts by state — which is genuine behavioral context. It omits pagination, ordering, and any auth/account-selection requirement.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single dense sentence, but the core fact (account campaigns) is front-loaded and every clause enumerates a real returned field that has no other documentation channel because there is no output schema. Nothing is repeated or decorative.

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 no-parameter, read-only list tool with no output schema, the description covers the one thing an agent needs: what each campaign object contains, including enum values for status and the signal research count states. Absent pagination or ordering details are not material to correct selection or invocation here.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-parameter tool applies. The description correctly avoids inventing filtering options that do not exist.

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 'The account's campaigns', making the resource and scope (account-level, unfiltered) explicit, and the title supplies the verb. It does not name or differentiate itself from sibling list tools such as list_golden_lists or get_prospect_list, so an agent cannot tell from the text alone which list tool to pick.

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

Usage Guidelines2/5

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

There is no statement of when to call this tool versus alternatives, no prerequisites, and no exclusions (e.g., whether it includes archived/paused campaigns or requires a campaign id elsewhere). 'Reads only' signals safety but not usage selection.

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