Skip to main content
Glama

get-legal-hold-content-items

Retrieve content items under legal hold for Miro Enterprise organizations to manage compliance and e-discovery cases.

Instructions

Retrieves the list of content items under legal hold (Enterprise only)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orgIdYesThe ID of the organization for which you want to retrieve the list of content items under hold
caseIdYesThe ID of the case for which you want to retrieve the list of content items under hold
legalHoldIdYesThe ID of the legal hold for which you want to retrieve the list of content items under hold
limitYesThe maximum number of items in the result list
cursorNoCursor for pagination

Implementation Reference

  • The asynchronous handler function that executes the tool logic by calling MiroClient.getApi().getLegalHoldContentItems with the provided parameters and handling the response or error.
      fn: async ({ orgId, caseId, legalHoldId, limit, cursor }) => {
        try {
          const query: any = {};
          if (cursor) query.cursor = cursor;
    
          const response = await MiroClient.getApi().getLegalHoldContentItems(
            orgId,
            caseId,
            legalHoldId,
            limit,
            query
          );
    
          return ServerResponse.text(JSON.stringify(response.body, null, 2));
        } catch (error) {
          process.stderr.write(`Error retrieving legal hold content items: ${error}\n`);
          return ServerResponse.error(error);
        }
      }
    };
  • Zod schema defining the input arguments for the tool: orgId, caseId, legalHoldId, limit, and optional cursor.
    args: {
      orgId: z.string().describe("The ID of the organization for which you want to retrieve the list of content items under hold"),
      caseId: z.string().describe("The ID of the case for which you want to retrieve the list of content items under hold"),
      legalHoldId: z.string().describe("The ID of the legal hold for which you want to retrieve the list of content items under hold"),
      limit: z.number().describe("The maximum number of items in the result list"),
      cursor: z.string().optional().nullish().describe("Cursor for pagination")
    },
  • src/index.ts:206-206 (registration)
    Registers the getLegalHoldContentItemsTool with the ToolBootstrapper instance.
    .register(getLegalHoldContentItemsTool)
  • src/index.ts:105-105 (registration)
    Imports the tool definition for registration.
    import getLegalHoldContentItemsTool from './tools/getLegalHoldContentItems.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 mentions 'Enterprise only,' hinting at access restrictions, but fails to describe key behaviors like pagination (implied by 'cursor' parameter), rate limits, authentication needs, or what the return format looks like. This leaves significant gaps for a tool with 5 parameters.

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, efficient sentence with zero waste—it directly states the tool's purpose and a key restriction. It's appropriately sized and front-loaded, 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 complexity (5 parameters, no annotations, no output schema), the description is incomplete. It lacks details on behavioral traits, output format, and usage context, making it inadequate for an agent to fully understand how to invoke and interpret results from this tool.

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%, providing full documentation for all parameters (orgId, caseId, legalHoldId, limit, cursor). The description adds no additional parameter semantics beyond what's in the schema, so it meets the baseline of 3 without compensating or adding 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 action ('retrieves') and resource ('list of content items under legal hold'), making the purpose understandable. However, it doesn't distinguish this tool from sibling tools like 'get-legal-hold' or 'get-all-legal-holds' beyond mentioning 'content items,' which provides some differentiation but not explicit comparison.

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 with 'Enterprise only,' indicating a usage restriction, but lacks explicit when-to-use advice, alternatives (e.g., vs. 'get-legal-hold'), or prerequisites. No context on when this tool is preferred over others is given.

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