miro-mcp-server

miro_get_frame_items

Read-only

Retrieve all items inside a Miro board frame. Filter by item type like sticky notes, shapes, or text to get only what you need.

Get all items contained within a specific frame. Filterable by type. For items in a logical group, use miro_get_group_items.

VOICE-FRIENDLY: "Frame has 8 items: 5 stickies, 2 shapes, 1 text"

TableJSON Schema

Name	Required	Description
`type`	No	Filter by item type: sticky_note, shape, text, card, image
`limit`	No	Max items to return (default 50, max 100)
`cursor`	No	Pagination cursor
`board_id`	Yes	Board ID
`frame_id`	Yes	Frame ID to get items from
`detail_level`	No	Response detail level: 'minimal' (default) returns basic fields, 'full' includes style, geometry, timestamps, and creator info

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`items`	Yes
`cursor`	No
`message`	Yes
`has_more`	Yes

A3.8/5.0

Behavior3/5

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

Annotations already indicate read-only; description adds no behavioral details beyond that.

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?

Extremely concise: three sentences plus a voice-friendly example, front-loaded.

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 output schema present, description covers essential aspects; missing minor guidance on pagination but schema covers it.

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 has 100% coverage with descriptions; description adds no new parameter insights.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the tool retrieves items within a frame, with filtering ability, and distinguishes from miro_get_group_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?

Provides one alternative (miro_get_group_items) but lacks guidance on when to use this versus other listing tools.

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

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/olgasafonova/miro-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server