Skip to main content
Glama

Exclude a list from campaigns

exclude_list

Use this when the people on a list, or anyone at the companies on a company list, such as current customers or competitors, should be left out of every campaign. Registers the list as an exclusion for the whole organization: from then on, campaigns enrolling people from their lists skip them, people added to the list later included. A company list covers the people whose record is linked to one of its companies. People a campaign already enrolled, and people added to a campaign one by one, are not covered. Only a people or company list the organization made can be excluded, and a list already excluded is refused. 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": {
      "listId": "<listId>"
    },
    "name": "exclude_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
listIdYesThe people list or company list to exclude: one your organization made.

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?

Beyond the annotations, the description discloses the organization-wide scope, future retroactivity (people added later are also covered), the coverage semantics for company lists, and the carve-outs for people already enrolled. It also states eligibility refusals and that the operation is free, which the annotations do not convey.

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 description is front-loaded with the usage trigger and stays dense, with no filler sentences. However, the middle sentences about company-list coverage and enrollment carve-outs are packed into one long block, so it is slightly wordier than it needs to be.

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 an organization-wide mutation with a single parameter and no output schema, the description covers scope, timing, eligibility, failure cases, and cost. Nothing an agent needs in order to decide whether to call it, or to predict its effect, is missing.

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 schema already documents listId at 100% coverage, so the baseline is 3. The description adds real meaning by explaining that either a people list or a company list is accepted, that company lists only cover people linked to those companies, and that the list must belong to the caller's organization.

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 description states a specific action and resource: it registers a people or company list as an organization-wide campaign exclusion. That is clearly differentiated from siblings such as remove_people_from_list and add_list_to_campaign, which act on individual people or attach lists to a single campaign.

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 strong when-to-use trigger (current customers, competitors that should be left out of every campaign) and several explicit when-not conditions: already-enrolled people, people added one by one, non-organization lists, and lists that are already excluded. It does not explicitly name a sibling alternative, so it falls short of a 5.

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