Skip to main content
Glama

delete-document-item

Remove a specific document from a Miro board by providing the board and item identifiers.

Instructions

Delete a specific document item from a Miro board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesUnique identifier (ID) of the board that contains the document
itemIdYesUnique identifier (ID) of the document that you want to delete

Implementation Reference

  • The handler function that executes the tool logic: validates boardId and itemId, calls MiroClient API to delete the document item, and returns success or error response.
    fn: async ({ boardId, itemId }) => {
      try {
        if (!boardId) {
          return ServerResponse.error("Board ID is required");
        }
        
        if (!itemId) {
          return ServerResponse.error("Item ID is required");
        }
    
        await MiroClient.getApi().deleteDocumentItem(boardId, itemId);
        return ServerResponse.text(JSON.stringify({ success: true, message: "Document item successfully deleted" }));
      } catch (error) {
        return ServerResponse.error(error);
      }
    }
  • ToolSchema definition including the tool name, description, and Zod input schema for parameters boardId and itemId.
    const deleteDocumentItemTool: ToolSchema = {
      name: "delete-document-item",
      description: "Delete a specific document item from a Miro board",
      args: {
        boardId: z.string().describe("Unique identifier (ID) of the board that contains the document"),
        itemId: z.string().describe("Unique identifier (ID) of the document that you want to delete")
      },
  • src/index.ts:145-145 (registration)
    Registration of the deleteDocumentItemTool in the ToolBootstrapper instance.
    .register(deleteDocumentItemTool)
  • src/index.ts:44-44 (registration)
    Import of the deleteDocumentItemTool for registration.
    import deleteDocumentItemTool from './tools/deleteDocumentItem.js';
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Delete' implies a destructive mutation, it doesn't specify whether this operation is reversible, what permissions are required, whether it affects related items, or what happens on success/failure. For a destructive tool with zero annotation coverage, this leaves critical behavioral traits undocumented.

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 a single, efficient sentence that states the core purpose without any wasted words. It's appropriately sized for a straightforward deletion tool and gets directly to the point with no unnecessary elaboration.

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

Completeness2/5

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

For a destructive mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address critical context like what 'delete' means operationally (permanent vs. soft delete), error conditions, authentication requirements, or what the agent should expect after invocation. The combination of destructive nature and lack of structured metadata demands more descriptive guidance.

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%, with both parameters clearly documented in the schema itself. The description doesn't add any meaningful parameter semantics beyond what's already in the schema descriptions for boardId and itemId. This meets the baseline expectation when schema coverage is complete.

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 specific action ('Delete') and target resource ('a specific document item from a Miro board'), distinguishing it from other deletion tools like delete-board or delete-item by specifying the document item type. It provides a precise verb+resource combination that leaves no ambiguity about what the tool does.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like delete-item (which might handle generic deletions) or other deletion tools for different item types. There's no mention of prerequisites, constraints, or comparison with sibling tools, leaving the agent to infer usage context from the tool name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/k-jarzyna/mcp-miro'

If you have feedback or need assistance with the MCP directory API, please join our Discord server