Skip to main content
Glama

delete_item

Destructive

Delete one text item, stroke or shape by ID. Shapes may be given as "shape" or their shape type. Requires an edit link and user confirmation.

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": {
      "boardUrl": "<boardUrl>",
      "type": "<type>",
      "id": "<id>",
      "confirm": "<confirm>"
    },
    "name": "delete_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
typeYes
confirmYesSet only after the user confirms deletion.
boardUrlYesA JotPond /b/<edit-id> or /view/<read-only-id> link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "text",
      -  "stroke"
      -]New value: +[
      +  "text",
      +  "stroke",
      +  "shape",
      +  "ellipse",
      +  "rectangle",
      +  "triangle",
      +  "line",
      +  "arrow"
      +]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds the key constraint that a /view/ read-only boardUrl will not work and that the user must confirm. It stops short of saying whether deletion is permanent or undoable, which matters for an irreversible mutation.

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, front-loaded with the action and resource, followed by the two hard prerequisites. Every clause carries information the caller 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 4-parameter destructive tool with annotations and no output schema, this covers the essentials: what gets deleted, how to address it, which link type works, and the confirmation gate. The only meaningful omission is whether the deletion can be undone.

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?

With only 50% schema description coverage, the description compensates by explaining that `type` accepts either the generic 'shape' or a concrete shape type, and that `id` refers to a single item. It also maps `boardUrl` to the edit-link requirement, though it adds nothing about `confirm` beyond what the schema already documents.

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?

The description gives a specific verb and scope: delete ONE text item, stroke, or shape, addressed by ID. The word 'one' implicitly distinguishes it from clear_board, which removes everything, but no sibling is named explicitly, so the differentiation depends on the agent's inference.

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

Usage Guidelines4/5

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

It states two concrete prerequisites: an edit link is required, and the user must confirm before the call. It does not say when to prefer this over clear_board or how to proceed if the user has only a read-only link, so there is clear context but no explicit alternatives.

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