Skip to main content
Glama

get-tag

Retrieve specific tag details from Miro boards to access labeling information and organize visual content effectively.

Instructions

Retrieve information about a specific tag on 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 retrieve

Implementation Reference

  • The handler function that executes the 'get-tag' tool logic, validating inputs and calling MiroClient.getApi().getTag to retrieve tag information.
    fn: async ({ boardId, tagId }) => {
      try {
        if (!boardId) {
          return ServerResponse.error("Board ID is required");
        }
    
        if (!tagId) {
          return ServerResponse.error("Tag ID is required");
        }
    
        const result = await MiroClient.getApi().getTag(boardId, tagId);
        return ServerResponse.text(JSON.stringify(result, null, 2));
      } catch (error) {
        return ServerResponse.error(error);
      }
    }
  • Zod schema defining the input parameters for the 'get-tag' tool: boardId and tagId.
    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 retrieve")
    },
  • src/index.ts:166-166 (registration)
    Registration of the 'get-tag' tool using ToolBootstrapper.register(getTagTool).
    .register(getTagTool)
  • src/index.ts:66-66 (registration)
    Import statement for the getTagTool module used in registration.
    import getTagTool from './tools/getTag.js';
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it's a retrieval operation, implying read-only behavior, but doesn't specify authentication requirements, rate limits, error conditions, or what 'information' includes (e.g., tag metadata, associated items). This leaves significant gaps for an agent to understand 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, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, making it easy to parse quickly.

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?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'information' is retrieved, potential return formats, or error handling. For a tool with two required parameters and no structured output, more context is needed to guide effective use.

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 clear parameter descriptions in the schema itself. The description adds no additional parameter details beyond implying the need for a specific tag, which is already covered by the schema. This meets the baseline for high schema coverage without 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 ('Retrieve information') and target ('about a specific tag on a Miro board'), making the purpose evident. However, it doesn't explicitly differentiate from sibling tools like 'get-all-tags' or 'get-item-tags', which would require a more specific scope comparison.

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?

No guidance is provided on when to use this tool versus alternatives. The description lacks context about prerequisites, such as needing a specific tag ID, and doesn't mention sibling tools like 'get-all-tags' for broader queries or 'get-item-tags' for tag associations.

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