Skip to main content
Glama

get_items

Read-only

List and filter Miro board items by type, IDs, or parent frame, returning compact content, position, size, and connector details for board inspection.

Instructions

List board items, filtered by type, ids and/or parentId (a frame id). Items come back compact: {id, type, content/title as plain text, x, y, width, height, parentId, fill (= style.fillColor), from/to (connector ends)}. x/y of an item with parentId are relative to the frame top-left. Pass full:true only if you need raw Web SDK fields.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNo
fullNo
typeNosticky_note, shape, text, card, app_card, frame, connector, image, embed, preview, group, curve (freehand drawing), unsupported (tables and other items the SDK cannot read)
parentIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.0
    • addedInput schema / properties / type / description
      Added value: +"sticky_note, shape, text, card, app_card, frame, connector, image, embed, preview, group, curve (freehand drawing), unsupported (tables and other items the SDK cannot read)"
    • removedInput schema / properties / type / items / enum
      Removed value: -[
      -  "sticky_note",
      -  "shape",
      -  "text",
      -  "card",
      -  "app_card",
      -  "frame",
      -  "connector",
      -  "image",
      -  "embed",
      -  "preview",
      -  "group"
      -]
  2. First observedv1.2.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), yet the description adds substantial behavior: the compact return shape with field-by-field mapping, the fact that fill aliases style.fillColor, and that x/y are frame-relative when parentId is set. The remaining gap is volume behavior — whether all items are returned or the result is capped/paginated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, followed by return shape, coordinate caveat, and the full flag — a sensible ordering with no filler sentences. The inline brace-delimited shape is dense but information-bearing; the middle sentence is long and carries several ideas at once.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly supplies the return shape and the non-obvious coordinate-frame semantics, which is exactly what an agent needs to interpret results. What is missing is result-size behavior (pagination or limits) for a list tool that is callable with zero filters.

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 coverage is only 25% (only `type` is documented inline), and the description does compensate by explaining parentId as "a frame id" and full as "raw Web SDK fields", plus that ids acts as a filter. It still adds no format detail for ids (validity, max length) or clarifying that the filters are ANDed, so compensation is partial.

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 opens with a specific verb+resource ("List board items") and immediately names the filter dimensions (type, ids, parentId), so an agent knows exactly what it retrieves. It never names a sibling to contrast with, so distinction from get_selection or get_board_info must be inferred from the word "board items".

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is real guidance for the non-obvious option: "Pass full:true only if you need raw Web SDK fields" explicitly warns against the heavier mode. However, there is no statement about when to prefer this over get_selection or get_focus, and no note on whether filters combine or whether omitting all filters returns the entire board.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.