Skip to main content
Glama

delete-tag

Remove a specific tag from a Miro board to organize content and maintain board clarity. Specify the board and tag IDs to delete unwanted tags.

Instructions

Delete a specific tag from a Miro board

Input Schema

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

Implementation Reference

  • The handler function that implements the core logic of the 'delete-tag' tool. It validates the boardId and tagId inputs, calls the Miro API to delete the tag, and returns a success or error response.
    fn: async ({ boardId, tagId }) => {
      try {
        if (!boardId) {
          return ServerResponse.error("Board ID is required");
        }
    
        if (!tagId) {
          return ServerResponse.error("Tag ID is required");
        }
    
        await MiroClient.getApi().deleteTag(boardId, tagId);
        return ServerResponse.text(JSON.stringify({ success: true, message: "Tag deleted successfully" }, null, 2));
      } catch (error) {
        return ServerResponse.error(error);
      }
    }
  • The ToolSchema definition for 'delete-tag', including the tool name, description, and Zod schemas for input parameters boardId and tagId.
    const deleteTagTool: ToolSchema = {
      name: "delete-tag",
      description: "Delete a specific tag from a Miro board",
      args: {
        boardId: z.string().describe("Unique identifier (ID) of the board that contains the tag"),
        tagId: z.string().describe("Unique identifier (ID) of the tag that you want to delete")
      },
  • src/index.ts:169-169 (registration)
    The registration of the deleteTagTool in the ToolBootstrapper chain in the main index file.
    .register(deleteTagTool)
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, the description doesn't specify whether this operation is reversible, what permissions are required, whether it affects associated items, or what happens on success/failure. This leaves significant gaps in understanding the tool's behavior.

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, clear sentence that efficiently communicates the core purpose without any wasted words. It's appropriately sized for a simple deletion operation and gets straight to the point.

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 insufficient. It doesn't address critical context like what 'delete' means operationally (permanent removal?), what happens to tagged items, whether there are confirmation requirements, or what the response contains. The agent would need to guess about important behavioral aspects.

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?

The input schema has 100% description coverage, with both parameters clearly documented. The description adds no additional parameter information beyond what's already in the schema descriptions, so it meets the baseline expectation but doesn't provide extra value regarding parameter usage or constraints.

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 clearly states the action ('Delete') and resource ('a specific tag from a Miro board'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'detach-tag' or 'delete-item', which could cause confusion about when to use this specific deletion tool versus others.

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. With sibling tools like 'detach-tag' (which removes tag associations) and 'delete-item' (which might delete tags among other items), the agent has no indication whether this tool is for permanent deletion versus disassociation, or whether it's the preferred method for tag removal.

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