Skip to main content
Glama

get-board-content-logs

Retrieve content change logs for Miro board items to track modifications, filter by date, board, or user, and monitor activity for enterprise organizations.

Instructions

Retrieves content change logs of board items (Enterprise only)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orgIdYesUnique identifier of the organization
fromYesStart date for filtering (ISO 8601 format)
toYesEnd date for filtering (ISO 8601 format)
boardIdsNoList of board IDs to filter by
emailsNoList of user emails to filter by
cursorNoCursor for pagination
limitNoMaximum number of results to return
sortingNoSort order for results

Implementation Reference

  • The handler function implementing the tool logic: constructs query parameters, converts dates, calls MiroClient's enterpriseBoardContentItemLogsFetch API, and returns the response or error.
    fn: async ({ orgId, from, to, boardIds, emails, cursor, limit, sorting }) => {
      try {
        const query: any = {};
        if (boardIds) query.boardIds = boardIds;
        if (emails) query.emails = emails;
        if (cursor) query.cursor = cursor;
        if (limit) query.limit = limit;
        if (sorting) query.sorting = sorting;
    
        // Convert string dates to Date objects
        const fromDate = new Date(from);
        const toDate = new Date(to);
    
        const response = await MiroClient.getApi().enterpriseBoardContentItemLogsFetch(
          orgId,
          fromDate,
          toDate,
          query
        );
    
        return ServerResponse.text(JSON.stringify(response.body, null, 2));
      } catch (error) {
        process.stderr.write(`Error retrieving board content logs: ${error}\n`);
        return ServerResponse.error(error);
      }
    }
  • Zod schema defining the input arguments for the 'get-board-content-logs' tool, including required orgId, from/to dates, and optional filters.
    args: {
      orgId: z.string().describe("Unique identifier of the organization"),
      from: z.string().describe("Start date for filtering (ISO 8601 format)"),
      to: z.string().describe("End date for filtering (ISO 8601 format)"),
      boardIds: z.array(z.string()).optional().nullish().describe("List of board IDs to filter by"),
      emails: z.array(z.string()).optional().nullish().describe("List of user emails to filter by"),
      cursor: z.string().optional().nullish().describe("Cursor for pagination"),
      limit: z.number().optional().nullish().describe("Maximum number of results to return"),
      sorting: z.enum(["asc", "desc"]).optional().nullish().describe("Sort order for results")
    },
  • src/index.ts:207-207 (registration)
    Registers the getBoardContentLogsTool instance with the ToolBootstrapper in the main server setup.
    .register(getBoardContentLogsTool);
  • src/index.ts:106-106 (registration)
    Imports the getBoardContentLogsTool from its module for registration.
    import getBoardContentLogsTool from './tools/getBoardContentLogs.js';
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 tool retrieves logs, implying a read-only operation, but doesn't clarify aspects like permissions required, rate limits, pagination behavior (beyond the cursor parameter in schema), or what the logs contain. This leaves significant gaps in understanding how the tool behaves in practice.

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 extremely concise with a single sentence that directly states the tool's function and restriction. It's front-loaded with the core purpose and wastes no words, making it easy for an agent to parse quickly without unnecessary elaboration.

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?

For a tool with 8 parameters, no annotations, and no output schema, the description is inadequate. It lacks details on behavioral traits (e.g., pagination, enterprise context), usage context compared to siblings, and expected return values. The high parameter count and absence of structured support fields mean the description should do more to guide the agent effectively.

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?

The schema description coverage is 100%, with each parameter well-documented in the input schema. The description adds no additional parameter details beyond what the schema provides, such as explaining relationships between parameters (e.g., how 'boardIds' and 'emails' interact). Given the high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate with extra semantic value.

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 tool's purpose with a specific verb ('Retrieves') and resource ('content change logs of board items'), and it specifies an enterprise-only restriction. However, it doesn't differentiate from sibling tools like 'get-audit-logs' or 'get-specific-board' that might also retrieve logs or board information, which prevents a perfect score.

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 minimal guidance by mentioning 'Enterprise only', but it doesn't explain when to use this tool versus alternatives like 'get-audit-logs' or 'get-specific-board' for related data. There's no mention of prerequisites, exclusions, or specific scenarios for usage, leaving the agent with little contextual direction.

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