Skip to main content
Glama

Delete an exclusion

delete_exclusion
DestructiveIdempotent

Use this when campaigns may write again to the people on an excluded list. Stops excluding it from the next enrollment on; the list itself is kept. The people it kept out are not enrolled by this call, but the next enrollment takes them: a running dynamic campaign does so within 30 minutes. 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": {
      "exclusionId": "<exclusionId>"
    },
    "name": "delete_exclusion"
  }
}

Input Schema

NameRequiredDescriptionDefault
exclusionIdYesThe exclusion's id, not its list's.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description adds genuinely new behavior: the list survives, no people are enrolled by the call itself, and a running dynamic campaign re-includes them within 30 minutes. It also notes the call is free. It stops short of saying whether the exclusion record is permanently gone or can be recreated, which is the remaining behavioral gap.

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?

Three sentences, all information-bearing, front-loaded with the when-to-use condition before the mechanical consequences. The phrasing 'Stops excluding it from the next enrollment on' is slightly awkward but still parses; nothing is padding.

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 one-parameter mutation with full annotation coverage and a fully documented schema, the description supplies everything an agent needs: the effect, what is preserved, what is not triggered immediately, and the timing for dynamic campaigns. No output schema exists and none is needed for a boolean-style delete.

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 the single parameter already carries the crucial disambiguation ('The exclusion's id, not its list's'). The description reinforces this indirectly by stressing the list is kept, but adds no format, sourcing, or lookup guidance beyond the schema, so the baseline 3 applies.

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 conveys a specific effect (an exclusion stops being applied so campaigns can write to those people again) and explicitly disambiguates from the sibling delete_list by noting 'the list itself is kept.' The only weakness is that it never states the operation in a plain verb+resource form, so the agent has to infer 'delete an exclusion' from the title plus effect.

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?

'Use this when campaigns may write again to the people on an excluded list' gives a clear triggering condition, and 'The people it kept out are not enrolled by this call' implicitly rules out the wrong expectation. No alternative tool is named for the opposite case (keeping the exclusion), but the condition is unambiguous enough to select correctly.

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