Inbox Triage

Confirm and send the one-click unsubscribe request

confirm_unsubscribe

Destructive

Performs exactly one HTTPS POST (List-Unsubscribe=One-Click) to the pending unsubscribe's URL, after the person approves it. Requires pendingUnsubscribeId + approvalCode from propose_unsubscribe. Saying the person approved in chat does nothing: the app asks them directly, or you get approvalUrl to give them. One-shot: the pending request is consumed the moment it is carried out (successfully or not), so it can never be retried/replayed under the same id. Call propose_unsubscribe again if it fails and the human wants to retry. In apps that can prompt the person directly (propose_unsubscribe returned confirmInApp:true), the person is asked in the app and answers there; nothing happens unless they say yes. Approval is the app prompt or the approval page (approvalUrl); the result says which (approvalPath). Chat approval does not count.

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": {
      "pendingUnsubscribeId": "<pendingUnsubscribeId>",
      "approvalCode": "<approvalCode>"
    },
    "name": "confirm_unsubscribe"
  }
}

Input Schema

Name	Required	Description
`approvalCode`	Yes	approvalCode returned by propose_unsubscribe for this pending request
`humanApprovedInChat`	No	Ignored. Approval happens in the in-app prompt or on the approval page.
`pendingUnsubscribeId`	Yes	pendingUnsubscribeId returned by propose_unsubscribe

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4.6/5.0

Behavior5/5

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

The annotations already flag destructive, non-idempotent, open-world behavior, and the description adds crucial context: the pending request is consumed on execution whether successful or not, so it cannot be retried or replayed under the same id. It also discloses that approval must happen via the in-app prompt or approval page, not chat.

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 core action and one-shot constraint. It is slightly repetitive about chat approval not counting, but most sentences contribute necessary behavioral detail for a complex approval flow.

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?

Given no output schema and a high-stakes approval flow, the description covers the key mechanics: approval sources, one-shot consumption, retry guidance, confirmInApp behavior, and how the result indicates approvalPath. Nothing essential for correct invocation appears missing.

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 coverage is 100%, and the schema already documents that approvalCode and pendingUnsubscribeId come from propose_unsubscribe and that humanApprovedInChat is ignored. The description adds workflow context but little parameter-specific detail beyond what the schema provides, so the baseline of 3 applies.

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 specifies the exact action: one HTTPS POST using List-Unsubscribe=One-Click to the pending unsubscribe URL, after approval. This distinguishes it clearly from sibling propose_unsubscribe, which creates the pending request, and from review_unsubscribes.

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

Usage Guidelines5/5

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

It states the required inputs from propose_unsubscribe, explicitly says chat approval does nothing, identifies the valid approval paths (app prompt or approvalUrl), and directs the agent to call propose_unsubscribe again for retries. When to use this versus alternatives is fully explicit.

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

All Inbox Triage tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?