Skip to main content
Glama

delete_items

Destructive

Delete Miro board items by ID, including their attached connectors, while tracking IDs that were already gone.

Instructions

Delete items by id. Deleting an item also deletes connectors attached to it; ids already gone are counted in alreadyGone.

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": {
      "ids": "<ids>"
    },
    "name": "delete_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag this as destructive and non-read-only, but the description adds two facts the annotations cannot convey: deletion cascades to attached connectors, and already-deleted ids are tolerated and reported via alreadyGone. That cascade warning is the key hidden consequence for a destructive tool. It stops short of stating irreversibility or permission requirements.

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 short sentences with zero waste; the core operation is front-loaded and the cascade side-effect follows immediately. Every clause carries information the agent needs.

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 single-parameter destructive tool with no output schema, the description covers the operation, the cascade consequence, and the alreadyGone result field well enough to call it correctly. Missing only peripheral details such as batch size limits or required permissions.

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?

One parameter with 0% schema description coverage, so the description must carry the burden. It says deletion is 'by id' and implies multiple ids are accepted (since some may be 'already gone'), but it never states that ids is a non-empty array, what id format is expected, or whether order matters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Delete items by id'), so the agent immediately knows the operation and its selector. Sibling names like create_items and update_items are distinct verbs, so no explicit differentiation is required, though none is offered.

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?

Usage is implied by the verb rather than stated: there is no explicit when-to-use, when-not-to-use, or pointer to a safer alternative. The note about ids already gone being counted does imply the call tolerates stale ids, but that is behavioral rather than routing guidance.

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