Skip to main content
Glama

get-embed-item

Retrieve details of a specific embed item on a Miro board using board and item IDs to access embedded content information.

Instructions

Retrieve information about a specific embed item on a Miro board

Input Schema

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

Implementation Reference

  • The handler function implementing the 'get-embed-item' tool logic. Validates inputs, calls Miro API to retrieve the embed item, formats the response, and handles errors.
    fn: async ({ boardId, itemId }) => {
      try {
        if (!boardId) {
          return ServerResponse.error("Board ID is required");
        }
    
        if (!itemId) {
          return ServerResponse.error("Item ID is required");
        }
    
        const result = await MiroClient.getApi().getEmbedItem(boardId, itemId);
        return ServerResponse.text(JSON.stringify(result, null, 2));
      } catch (error) {
        return ServerResponse.error(error);
      }
    }
  • Schema definition for the 'get-embed-item' tool, including name, description, and Zod schemas for input parameters boardId and itemId.
    const getEmbedItemTool: ToolSchema = {
      name: "get-embed-item",
      description: "Retrieve information about a specific embed item on a Miro board",
      args: {
        boardId: z.string().describe("Unique identifier (ID) of the board that contains the embed"),
        itemId: z.string().describe("Unique identifier (ID) of the embed that you want to retrieve")
      },
  • src/index.ts:62-62 (registration)
    Import statement for the getEmbedItemTool module.
    import getEmbedItemTool from './tools/getEmbedItem.js';
  • src/index.ts:162-162 (registration)
    Registration of the getEmbedItemTool in the ToolBootstrapper instance.
    .register(getEmbedItemTool)
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Retrieve information' which implies a read-only operation, but doesn't disclose behavioral traits like authentication requirements, rate limits, error conditions, or what specific information is returned. This is inadequate for a tool with no annotation coverage.

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's front-loaded and wastes no space, making it easy for an agent 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 no annotations and no output schema, the description is insufficiently complete. It doesn't explain what information is retrieved (e.g., embed details, metadata), potential side effects, or error handling, leaving significant gaps for a tool that interacts with board items.

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 ('boardId' and 'itemId') clearly documented in the schema. The description adds no additional meaning beyond the schema, such as format examples or contextual usage, so it meets the baseline for high schema coverage.

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 resource ('specific embed item on a Miro board'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'get-specific-item' or 'get-items-on-board' that might retrieve similar items, so it doesn't achieve full sibling distinction.

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 'get-specific-item' or 'get-items-on-board' from the sibling list. It lacks any context about prerequisites, exclusions, or comparative use cases, leaving the agent to infer usage.

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