clippy

Delete Clippy Item

delete-item-tool

Destructive

Delete a single item from a Clippy room by its item id (the id returned by store-item / list-items). Any images attached to the item are removed too. This cannot be undone.

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": {
      "room": "<room>",
      "item_id": "<item_id>"
    },
    "name": "delete-item-tool"
  }
}

Input Schema

Name	Required	Description
`room`	Yes	The 6-character room code (or a Clippy share URL / #CODE link).
`item_id`	Yes	The item id (UUID) to delete.
`password`	No	Required only if the room is password-protected and you are not using owner_token.
`owner_token`	No	Optional. The room owner_token; bypasses the password on a locked room.

Output Schema

Name	Required	Description	Default
`code`	Yes	The room code that was targeted.
`deleted`	Yes	Whether an item was actually deleted (false if it did not exist).

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 12, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses two additional behaviors: that images attached to the item are also removed, and that the action cannot be undone. This adds significant behavioral context for the agent.

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 two sentences, front-loading the core action in the first sentence and adding side effects in the second. Every word earns its place with no redundancy.

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?

The description covers the main behavior (deletion, image removal, irreversibility) and references where to get the item_id. It doesn't explain error conditions or permission handling, but with an output schema present and simple semantics, this is sufficient.

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

Parameters4/5

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

While schema coverage is 100%, the description adds value by specifying that the item_id is the one 'returned by store-item / list-items', which is not in the schema. It also notes images are removed, adding context not found in parameter descriptions.

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 action ('delete a single item') and the resource ('from a Clippy room'), specifying how to identify the item by its 'item id' and referencing the id from other tools. It distinguishes itself from sibling tools by specifying 'single item' as opposed to clearing all items.

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

Usage Guidelines3/5

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

The description implicitly suggests usage for deleting one item via 'single item', but it does not explicitly state when to use this tool versus alternatives like clear-room-tool. It provides no exclusion criteria or comparison to siblings, leaving the agent to infer context.

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

All clippy 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?