Skip to main content
Glama

Add a list to a campaign

add_list_to_campaign
DestructiveIdempotent

Use this when the user wants one more people list written to by a campaign, which holds up to 10 lists. In a running campaign the list's people are enrolled in the background and start receiving its messages, so confirm with the user first; in a draft they are enrolled at launch. A list the campaign already has is reported as already present. 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>",
      "listId": "<listId>"
    },
    "name": "add_list_to_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
listIdYesOne of your people lists.
campaignIdYesThe campaign's id.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the 10-list cap, that people in a running campaign are enrolled in the background and start receiving messages, that draft enrollments happen at launch, the already-present dedupe outcome, and that the call is free. The confirm-with-user warning is consistent with destructiveHint=true and the enrollment side effect that annotations alone do not explain.

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?

Front-loaded with the usage trigger, then the running-vs-draft behavior, then the dedupe outcome and the one-word cost note. Dense and well ordered, though the 'Free.' fragment and the multi-clause running-campaign sentence make it slightly denser than needed.

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 two-parameter mutation with no output schema, the description covers the cap, both campaign states, the idempotent 'already present' result, and the cost model. An agent has everything needed to call it correctly and warn the user.

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 100% and both parameters are documented there, so the schema carries the param-level meaning. The description adds only the implicit constraint that the list must be one the campaign does not already hold; it adds no format or identifier detail beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ('one more people list written to by a campaign') plus the hard cap of 10 lists, which lets an agent separate it from the person-level siblings such as add_people_to_campaign and add_people_to_list 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?

Gives a clear triggering condition ('Use this when the user wants one more people list...') and a confirm-first rule for running campaigns. It does not explicitly name an alternative tool or say when not to use this one, so the routing guidance is clear but not fully discriminating.

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