Skip to main content
Glama

get-image-item

Retrieve details about a specific image on a Miro board using board and image IDs to access visual content information.

Instructions

Retrieve information about a specific image item on a Miro board

Input Schema

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

Implementation Reference

  • The async handler function implementing the core logic of the 'get-image-item' tool: validates boardId and itemId, fetches the image item via MiroClient API, and returns JSON response or error.
    fn: async ({ boardId, itemId }) => {
      try {
        if (!boardId) {
          return ServerResponse.error("Board ID is required");
        }
    
        if (!itemId) {
          return ServerResponse.error("Item ID is required");
        }
    
        // Use generic getItem for image item
        const result = await MiroClient.getApi().getImageItem(boardId, itemId);
        return ServerResponse.text(JSON.stringify(result, null, 2));
      } catch (error) {
        return ServerResponse.error(error);
      }
    }
  • The ToolSchema definition providing the tool name, description, and Zod-validated input schema for boardId and itemId parameters.
    const getImageItemTool: ToolSchema = {
      name: "get-image-item",
      description: "Retrieve information about a specific image item on a Miro board",
      args: {
        boardId: z.string().describe("Unique identifier (ID) of the board that contains the image"),
        itemId: z.string().describe("Unique identifier (ID) of the image that you want to retrieve")
      },
  • src/index.ts:153-153 (registration)
    Registers the getImageItemTool with the ToolBootstrapper instance, making the 'get-image-item' tool available to the MCP server.
    .register(getImageItemTool)
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 the tool retrieves information, implying a read-only operation, but doesn't disclose behavioral traits like authentication needs, rate limits, error conditions, or what specific information is returned (e.g., metadata, content). This leaves gaps for a tool with no output schema.

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 front-loads the core purpose without unnecessary words. It's appropriately sized for a simple retrieval tool, with zero waste or redundancy.

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 incomplete. It doesn't explain what information is retrieved (e.g., image details, metadata), potential errors, or behavioral context, making it inadequate for a tool that likely returns complex data about an image item.

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 implying these IDs are required to locate the image, matching 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 image item on a Miro board'), making the purpose evident. However, it doesn't explicitly differentiate from sibling tools like 'get-specific-item' or 'get-items-on-board', which might retrieve similar or broader information.

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 such as 'get-specific-item' (which might retrieve any item type) or 'get-items-on-board' (which lists multiple items). The description lacks context on prerequisites or exclusions, leaving usage unclear relative to siblings.

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