Skip to main content
Glama
Michaelzag

Migadu MCP Server

by Michaelzag

delete_forwarding

DestructiveIdempotent

Remove email forwarding rules for specified addresses. Provide mailbox, forwarding address, and optional domain to eliminate unwanted forwards.

Instructions

Delete forwarding(s). DESTRUCTIVE. List of dicts with: mailbox, address, domain (optional).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes
Behavior3/5

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

The annotation already declares destructiveHint=true. The description adds 'DESTRUCTIVE' which aligns with that. It also describes the input structure (list of dicts with keys), but does not disclose further behavioral traits like error handling or partial failure behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with one sentence and a short list. It front-loads the purpose ('Delete forwarding(s)') and immediately provides essential parameter structure. No unnecessary words.

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?

Given the simplicity of the tool (delete with one parameter), the description covers the essential input format. It does not explain what a forwarding is or mention any side effects, but given sibling context and annotations, it is nearly complete. A minor gap is not explicitly stating that mailbox and address are required.

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?

The input schema has 0% description coverage. The description partially compensates by stating that 'items' is a list of dicts with keys mailbox, address, and optional domain. However, it does not specify which are required or provide types/validation rules.

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 clearly states the verb (delete), the resource (forwarding(s)), and hints at the input format. It distinguishes from sibling tools like delete_alias or delete_mailbox by specifying 'forwarding'.

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?

No guidance on when to use this tool versus alternatives like update_forwarding or list_forwardings. No prerequisites or usage context provided beyond the basic operation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Michaelzag/migadu-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server