Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Enroll campaign people

enroll_campaign_people
Idempotent

Enrolls people on a campaign's Golden List into its email sequence, excludes restricted companies, and lists skipped recipients with reasons; when sending is off, enrollments wait.

Instructions

Enrolls people on a campaign's Golden List in its email sequence: everyone not yet enrolled, or up to limit. Excluded people and restricted companies are never enrolled; anyone the sequence cannot email is listed in skipped with the reason. While sending is off, enrolling sends nothing and people wait, ready. While sending is on, their first email goes out about fifteen minutes later. A person's custom first email from signal research replaces Email 1 for them. Returns enrolled_count, skipped, remaining and the get_campaign_email shape.

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": "enroll_campaign_people"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost people to enroll in this call. Omitted: everyone not enrolled yet, up to 1,000.
campaign_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, the description discloses substantial behavior: excluded people and restricted companies are never enrolled, unemailable people appear in skipped with a reason, enrollment is inert while sending is off, first emails go out about fifteen minutes after sending is on, and custom first emails replace Email 1. These are exactly the operational details an agent needs before invoking a mutation with idempotentHint=true.

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?

The description is front-loaded with the core action, then layers scope, exclusions, sending-state behavior, and return fields in a compact sequence. Every sentence carries operational meaning without repetition.

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?

Although there is no output schema, the description names the returned fields (enrolled_count, skipped, remaining) and the get_campaign_email shape. Combined with its explanation of exclusions and sending-state behavior, it is complete for a two-parameter enrollment mutation.

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%: limit is already well documented in the schema, and campaign_id is undocumented there but obvious from context. The description reinforces the limit semantics ('everyone not yet enrolled, or up to limit') but adds little formal meaning beyond what the schema already provides.

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 states a specific verb and resource: enrolls people on a campaign's Golden List into its email sequence. It is clear what the tool does and how it differs in spirit from a generic add-people sibling, though it does not explicitly name or contrast with add_people_to_campaign.

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 by the enrollment scope ('everyone not yet enrolled, or up to limit') and the exclusions, but there is no explicit when-to-use versus when-not-to-use guidance or named alternative such as add_people_to_campaign. An agent can infer the context but is not routed between siblings.

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