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';
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