Skip to main content
Glama
deenesjakoruzh
k-jarzyna

Miro MCP

by k-jarzyna
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

delete-frame-item

Remove a frame from a Miro board by specifying the board ID and frame ID to clean up workspace organization.

Instructions

Delete a frame from a Miro board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesUnique identifier (ID) of the board from which you want to delete the frame
itemIdYesUnique identifier (ID) of the frame that you want to delete

Implementation Reference

  • src/tools/deleteFrameItem.ts:13-31 (handler)
    Handler function implementing the logic to delete a frame item from a Miro board using MiroClient API.
    fn: async ({ boardId, itemId }: {
  boardId: string,
  itemId: string
}) => {
  try {
    if (!boardId) {
      return ServerResponse.error("Board ID is required");
    }

    if (!itemId) {
      return ServerResponse.error("Item ID is required");
    }

    await MiroClient.getApi().deleteFrameItem(boardId, itemId);
    return ServerResponse.text(JSON.stringify({ success: true, message: "Frame successfully deleted" }, null, 2));
  } catch (error) {
    return ServerResponse.error(error);
  }
}
  • src/tools/deleteFrameItem.ts:9-12 (schema)
    Zod input schema defining required boardId and itemId parameters for the delete-frame-item tool.
    args: {
  boardId: z.string().describe("Unique identifier (ID) of the board from which you want to delete the frame"),
  itemId: z.string().describe("Unique identifier (ID) of the frame that you want to delete")
},
  • src/index.ts:141-141 (registration)
    Registers the delete-frame-item tool (imported as deleteFrameItemTool) with the ToolBootstrapper in the main index file.
    .register(deleteFrameItemTool)

Tool Definition Quality

C2.9/5.0
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 the action is a deletion, implying a destructive operation, but doesn't mention critical details like whether deletion is permanent, requires specific permissions, or has side effects (e.g., affecting other board elements). This leaves significant gaps for safe agent usage.

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, direct sentence with zero wasted words, front-loading the key action and resource. It's appropriately sized for a simple tool, 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 tool's destructive nature and lack of annotations or output schema, the description is incomplete. It fails to address behavioral aspects like permanence, error conditions, or return values, which are crucial for an agent to invoke it correctly and safely in context.

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 clear descriptions for both parameters (boardId and itemId). The description doesn't add any additional meaning beyond what the schema provides, such as format examples or constraints, but the schema adequately covers the basics, meeting the baseline for high 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 ('Delete') and resource ('a frame from a Miro board'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'delete-item' or 'delete-frame-item' (which appears to be itself), leaving room for ambiguity about scope.

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 'delete-item' or other deletion tools in the sibling list. The description lacks context about prerequisites, permissions, or scenarios where this specific tool is appropriate.

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