Skip to main content
Glama

List exclusions

list_exclusions
Read-only

Use this when the user asks what all their campaigns leave out and how often those exclusions have kept people out so far, or before excluding a list. Returns the organization's exclusions: the people lists and company lists whose people campaigns skip when they enroll from their lists, with the number of checks that skipped a person and, for a company list, the companies matched. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_exclusions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful context beyond that: the result is scoped to the organization, includes skipped-check counts, includes matched companies for company lists, and notes that the call is free.

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 then explains the return, with no filler. It is a little dense as a single long sentence, and the terminal 'Free.' is terse, but it still earns its place by clarifying cost.

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?

For a zero-parameter, read-only tool with no output schema, the description covers purpose, usage, scope, and the key returned fields. A fully structured breakdown of the response would be nice, but the present coverage is sufficient for an agent to call it correctly.

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?

There are zero input parameters, so parameter semantics carry no burden and the baseline is 4. The description instead spends its words on the return shape, which is appropriate for a parameterless list tool.

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 verb and resource: it returns the organization's exclusions, specifically people lists and company lists that campaigns skip during enrollment. It also distinguishes this from the act of excluding a list, so an agent can tell it apart from sibling tools like exclude_list without opening a 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 clear when-to-use guidance: when the user asks what campaigns leave out and how often, or before excluding a list. It stops short of explicitly naming exclude_list as the alternative or stating when not to use this tool, so it is strong but not fully exhaustive.

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