Skip to main content
Glama

Delete an inbox item

delete_inbox_item
DestructiveIdempotent

Remove ONE item from the user's Habidu Inbox by id (from get_inbox, preferred) or by exact title (case-insensitive) - when it is done, unwanted, or was just scheduled with create_task. For a scheduled task use delete_task. Returns {ok:true, removed:true, id}; ok:false with not_found means nothing was removed. A removed item cannot be restored. Not preview-gated.

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": "delete_inbox_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoThe Inbox item id from get_inbox. Preferred: exact.
titleNoThe item's title when you have no id, e.g. "Buy stamps" (case-insensitive exact match).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Goes well beyond the annotations by declaring irreversibility ("A removed item cannot be restored"), the return contract ("{ok:true, removed:true, id}"), the not_found failure meaning, and that it is "Not preview-gated." The annotations already cover destructive/idempotent/closed-world, so this extra disclosure is genuine added context; only the case of supplying both id and title is left implicit.

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?

Front-loaded with the core action and captures a lot in one dense sentence: source, fallback, triggers, sibling alternative, return shape, and irreversibility. Slightly clause-heavy but nearly every clause carries operational meaning.

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?

With no output schema, the description supplies the return shape and the not_found semantics, and it covers safety and alternatives for a destructive tool. Only the behavior when both or neither of id and title are provided is unaddressed.

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 both parameters are described there, so the description largely restates the same preference and case-insensitivity rules. It does not address the gap that no parameter is required, meaning an agent could call with neither id nor title and get an undocumented failure mode.

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?

States a specific verb and resource ("Remove ONE item from the user's Habidu Inbox") and immediately distinguishes itself from delete_task, which handles scheduled tasks. The uppercase "ONE" plus the id/title selection rule makes the scope unmistakable.

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?

Gives explicit when-to-use conditions ("when it is done, unwanted, or was just scheduled with create_task") and an explicit routing alternative ("For a scheduled task use delete_task"). It also names get_inbox as the source of the preferred identifier, so an agent knows the upstream call.

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