Skip to main content
Glama
Pombus MCP Server

Pombus MCP Server

Official

Remove allow/block entry

delete_list_entry
DestructiveIdempotent

Remove an email address from an inbox's allow or block list to manage message filtering permissions.

Instructions

Remove an address from an inbox's allow or block list.

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": {
      "inbox_id": "<inbox_id>",
      "direction": "<direction>",
      "list_type": "<list_type>",
      "entry": "<entry>"
    },
    "name": "delete_list_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
entryYes
inbox_idYesAn inbox id previously returned by list_inboxes. The server rejects any id outside this key's scope.
directionYes
list_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond the title: it does not say whether removal is irreversible, whether a missing entry errors or no-ops, or whether a re-add is required to undo.

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?

A single front-loaded sentence with no filler, which is the right shape for a narrow tool. Its brevity is efficient rather than padded, though the same word budget could have carried one clarifying clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a destructive, four-required-parameter mutation with no output schema and three undocumented parameters, and the description leaves the agent without the vocabulary needed to fill direction, list_type or entry correctly. It is materially under-specified for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 25%, with only inbox_id documented, and the description does not compensate. It never explains what 'direction' means (the send/receive axis), what 'list_type' selects (allow vs block), or the expected format of 'entry' (bare address vs domain).

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 gives a specific verb ("Remove") and a specific resource ("an address from an inbox's allow or block list"), which distinguishes it from create_list_entry and from inbox-level deletes like delete_inbox. It never names a sibling explicitly, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus create_list_entry or list_list_entries, no prerequisites, and no statement about what happens if the entry is not present. The only implied context is that the address must already exist on an allow or block list.

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