Skip to main content
Glama

detach-tag

Remove a tag from a specific item on a Miro board by providing board, tag, and item identifiers.

Instructions

Detach a tag from an item on a Miro board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesUnique identifier (ID) of the board that contains the tag and item
tagIdYesUnique identifier (ID) of the tag that you want to detach
itemIdYesUnique identifier (ID) of the item from which you want to detach the tag

Implementation Reference

  • The main handler function that implements the detach-tag tool logic: validates required parameters (boardId, tagId, itemId), calls MiroClient.getApi().removeTagFromItem, and returns success or error response.
    fn: async ({ boardId, tagId, itemId }) => {
      try {
        if (!boardId) {
          return ServerResponse.error("Board ID is required");
        }
    
        if (!tagId) {
          return ServerResponse.error("Tag ID is required");
        }
    
        if (!itemId) {
          return ServerResponse.error("Item ID is required");
        }
    
        // Use the SDK method to detach a tag from an item
        await MiroClient.getApi().removeTagFromItem(boardId, itemId, tagId);
        return ServerResponse.text(JSON.stringify({ success: true, message: "Tag detached successfully" }, null, 2));
      } catch (error) {
        return ServerResponse.error(error);
      }
    }
  • ToolSchema defining the tool name, description, and input parameters schema using Zod for boardId, tagId, and itemId.
    const detachTagTool: ToolSchema = {
      name: "detach-tag",
      description: "Detach a tag from an item on a Miro board",
      args: {
        boardId: z.string().describe("Unique identifier (ID) of the board that contains the tag and item"),
        tagId: z.string().describe("Unique identifier (ID) of the tag that you want to detach"),
        itemId: z.string().describe("Unique identifier (ID) of the item from which you want to detach the tag")
      },
  • src/index.ts:171-171 (registration)
    Registers the detachTagTool instance with the ToolBootstrapper server chain.
    .register(detachTagTool)
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. It states the action ('detach') which implies a mutation, but doesn't clarify permissions needed, whether the operation is reversible, what happens if the tag isn't attached, or any rate limits. This leaves significant gaps for a mutation tool.

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 straightforward operation and gets directly 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 mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after detachment, whether the tag persists independently, what error conditions might occur, or what the tool returns. The 100% schema coverage helps with parameters, but behavioral context is critically lacking.

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 schema description coverage is 100%, with all three parameters clearly documented in the schema itself. The description doesn't add any additional parameter context beyond what's already in the schema descriptions, so it meets the baseline expectation but doesn't provide extra value.

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 ('detach') and target resources ('tag from an item on a Miro board'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from its sibling 'attach-tag' or other tag-related tools like 'delete-tag', which would be needed for a perfect score.

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-tag' (which removes a tag entirely) or 'update-tag' (which might modify tag properties). There's no mention of prerequisites, error conditions, or typical use cases.

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