Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Get campaign results

get_campaign_results
Read-onlyIdempotent

Retrieve a campaign's read-only results—prospects found and reviewed, emails sent and replies received, signals, daily sends, and research progress—to review outreach performance and activity.

Instructions

A campaign's results, as its Results tab shows them: prospects found and reviewed, signals, emails prepared, enrolled, sent and replied (personal and automatic replies apart), sends per day, every sent email with its person, mailbox, step and outcome, every reply with its sender, subject and kind, research progress and the last search. Sent is a recorded provider send, not an open or inbox receipt. Reads only.

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

Input Schema

NameRequiredDescriptionDefault
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, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious semantics beyond that: the definition of 'sent' as a recorded provider send rather than an open or inbox receipt, and the separation of personal from automatic replies. It does not address volume limits or pagination for the 'every sent email' list, which is the main remaining behavioral unknown.

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 resource is front-loaded in the first clause and the rest of the sentence is a dense inventory of returned fields, so wording is largely load-bearing. It is a long run-on enumeration with some listing redundancy, but no sentence is wasted on filler or restating the title.

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?

There is no output schema, so the description must carry the return-value burden, and it does so thoroughly by enumerating counters, per-email records, per-reply records and research state. Combined with annotations covering the safety profile, an agent has enough to call it and interpret results. Missing only scale/pagination expectations for potentially large result sets.

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 0%, so campaign_id is documented only by its type (integer, exclusiveMinimum 0). The description's phrase 'A campaign's results' implicitly ties the parameter to selecting the campaign, but adds no syntax, format, or failure-mode guidance (e.g. behavior for an unknown or inaccessible id). With only one largely self-evident parameter, this is a minimum-viable 3 rather than a serious deficiency.

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 names a specific resource (a campaign's results) and enumerates precisely what is returned: prospects, signals, emails prepared/enrolled/sent/replied, per-day send counts, per-email detail and research progress. It is clearly a read of aggregated campaign outcome data, which separates it from write-oriented siblings like enroll_campaign_people or start_campaign_sending. It stops short of naming a read-side alternative (e.g. get_campaign_email) as a routing contrast, so it is a strong 4 rather than a 5.

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 implied only through the framing 'as its Results tab shows them', which signals this is the dashboard-style aggregate read. There is no explicit statement of when to prefer this over sibling reads such as get_campaign_email or get_email_sequence, and no preconditions or exclusions are given. An agent can infer the use case but must guess at the boundaries.

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