Skip to main content
Glama

Add people to a campaign

add_people_to_campaign
DestructiveIdempotent

Use this when the user wants specific people enrolled in a running campaign without putting them on one of its lists. Enrolls 1 to 60 people by id and starts their sequence, so they start receiving its messages: confirm with the user first. Each person comes back with an outcome, such as added, already in the campaign, or missing a valid work email. No email address is looked up here. A draft or paused campaign is refused. Calling again enrolls nobody twice. Free.

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": {
      "campaignId": "<campaignId>",
      "personIds": "<personIds>"
    },
    "name": "add_people_to_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
personIdsYes1 to 60 people, each once: the `id` of their rows in a list, or the ids an upload or enrichment answered with.
campaignIdYesThe campaign's id.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description contributes substantially beyond them: it demands user confirmation before enrolling, states no email address is looked up, that draft or paused campaigns are rejected, that repeat calls enroll nobody twice, and that each person returns an outcome (added, already in campaign, missing valid work email). That is precisely the behavioral context an agent needs to call a destructive mutation safely.

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?

Six short sentences, front-loaded with the use case before constraints and outcomes, and each one carries distinct information. The one-word closing "Free." is abrupt and reads awkwardly out of context, but it does convey that the call has no cost, so it is not truly wasteful.

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?

There is no output schema, and the description compensates by listing the per-person outcome values an agent will get back. Combined with the batch limit, confirmation requirement, and campaign-state precondition, nothing material is missing for a two-parameter, destructive mutation.

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?

Schema coverage is 100%, so the baseline is 3, and the description clears it by clarifying that 1 to 60 people are supplied by id and that "No email address is looked up here" — telling the agent not to pass addresses even though the person object may carry one. It adds no further syntax detail beyond that, which the schema already 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 definition gives a specific verb+resource ("Enrolls 1 to 60 people by id and starts their sequence") and scopes it with "enrolled in a running campaign without putting them on one of its lists," which separates it from the list-oriented siblings such as add_people_to_list and add_list_to_campaign. An agent can tell what this does without opening any schema.

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

Usage Guidelines4/5

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

It gives a clear triggering condition ("when the user wants specific people enrolled in a running campaign without putting them on one of its lists") and effective exclusions ("A draft or paused campaign is refused"). It does not name the alternative tool an agent should prefer for the list-based path, so the user must reason from the exclusion rather than a named redirect.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources