Mondovo

Delete an item from a collection

delete_collection_item

DestructiveIdempotent

Permanently delete ONE item from a collection. Name it by item_id, or by collection_type plus its slug or exact title. To hide an item without losing it, set it to draft with update_collection_item instead.

Input Schema

Name	Required	Description
`item`	No	The item's slug, or its exact current title. A title shared by several items is refused with their slugs.
`item_id`	No	The item's id (from list_collection_items). Preferred.
`site_id`	Yes	The site the collection belongs to
`user_goal`	No	Optional: the user's goal behind this call, in one short sentence of plain words (e.g. "add a page so customers can book tables"). No names, emails or other personal details.
`collection_type`	No	The collection, when naming the item by `item` instead of `item_id`.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

addedInput schema / properties / user_goal

Added value: +{
+  "description": "Optional: the user's goal behind this call, in one short sentence of plain words (e.g. \"add a page so customers can book tables\"). No names, emails or other personal details.",
+  "type": "string"
+}

First observedOct 19, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is carried structurally. The description still earns credit by reinforcing permanence and by implying the operation is scoped to one item only. It does not cover permissions, cascade effects on related data, or what a successful call returns.

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?

Two sentences, no filler, with the destructive-persistence warning and the single-item scope front-loaded before the alternative path. Every clause carries either scope, routing, or safety information.

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?

For a 5-parameter delete tool with full schema coverage and annotations covering destructiveness, the description covers enough to call it correctly. Remaining gaps — no output schema and no statement of side effects on related records — are minor but real for a permanent destructive operation.

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?

Schema coverage is 100%, so baseline is 3, but the description adds genuine semantics: item_id is preferred, and collection_type is only meaningful when addressing the item by slug/title. That pairing rule is behavioral guidance the flat schema does not state.

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 ("Permanently delete ONE item from a collection") with explicit scope — a single item, not the collection. That distinguishes it from delete_collection and makes the unit of deletion unambiguous to an agent scanning siblings.

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?

Names the safer alternative explicitly ("To hide an item without losing it, set it to draft with update_collection_item instead") and gives the condition that selects it. It also states the two valid identification paths — item_id, or collection_type plus slug/exact title — so the agent knows how to invoke it, not just when.

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

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