Skip to main content
Glama

Move a diagram to the trash

delete_diagram
DestructiveIdempotent

Moves a diagram to the trash at the person’s request; the person can restore it in Archboard. It cannot delete permanently, and it is meant only for a diagram the person asked to delete. Works only where the diagram’s permission (list_workspaces, list_diagrams, get_canvas) is delete, which needs Delete chosen for this app under Settings → Connected apps; where it is read or write, the call is refused (such as forbidden with grant_permission) and nothing is moved. Returns trashed, diagramId, title, deletedAt and userMessage (a confirmation for the person, in their language).

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": {
      "diagramId": "<diagramId>"
    },
    "name": "delete_diagram"
  }
}

Input Schema

NameRequiredDescriptionDefault
diagramIdYesDiagram id (from list_diagrams or create_diagram).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, but the description adds critical context beyond structured fields: the operation is a restorable trash move, requires an explicit 'delete' permission grant that must be enabled in Settings, and returns specific fields including a localized userMessage. This is rich behavioral detail that meaningfully informs invocation.

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?

The description is front-loaded with the core action and scope, then adds permission and return-value details. It is dense but every clause contributes necessary context; there is no filler, though it could be slightly more scannable with sentence breaks.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having only one parameter and no output schema, the description covers the soft-delete behavior, permission prerequisites, failure modes, and return fields. Together with the annotations, an agent has everything needed to call the tool correctly and understand its effects.

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 description coverage is 100%, so the single diagramId parameter is already fully documented in the schema. The description adds no further syntax or format details for the parameter beyond what the schema provides, which meets the baseline for high-coverage schemas.

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 states a specific verb and resource ('Moves a diagram to the trash') and clarifies the soft-delete scope ('cannot delete permanently'), which distinguishes it from siblings like create_diagram or revert_change. An agent can immediately understand the action without opening the schema.

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?

It gives explicit when-to-use ('at the person’s request', 'only for a diagram the person asked to delete') and when-not-to-use via the permission requirement ('where it is read or write, the call is refused... and nothing is moved'). The condition that selects this tool over alternatives is clear.

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.