Skip to main content
Glama

retrieve_multiple_collaborators

Get a paginated list of collaborators in a Storyblok space. Specify page and per_page parameters to control the results.

Instructions

Retrieves a paginated list of collaborators (users) in a specified Storyblok space.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number
per_pageNoItems per page

Implementation Reference

  • The registerCollaborators function registers all collaborator tools including 'retrieve_multiple_collaborators' on the MCP server.
    export function registerCollaborators(server: McpServer): void {
      // Tool: retrieve_multiple_collaborators
      server.tool(
        'retrieve_multiple_collaborators',
        'Retrieves a paginated list of collaborators (users) in a specified Storyblok space.',
        {
          page: z.number().optional().default(1).describe('Page number'),
          per_page: z.number().optional().default(25).describe('Items per page'),
        },
        async ({ page, per_page }) => {
          try {
            const params: Record<string, string> = {
              page: String(page ?? 1),
              per_page: String(per_page ?? 25),
            };
            const data = await apiGet('/collaborators/', params);
            return createJsonResponse(data);
          } catch (error) {
            if (error instanceof APIError) {
              return createErrorResponse(error);
            }
            throw error;
          }
        }
      );
  • The 'retrieve_multiple_collaborators' tool handler function that accepts optional page/per_page params and calls apiGet('/collaborators/') to fetch a paginated list of collaborators.
    // Tool: retrieve_multiple_collaborators
    server.tool(
      'retrieve_multiple_collaborators',
      'Retrieves a paginated list of collaborators (users) in a specified Storyblok space.',
      {
        page: z.number().optional().default(1).describe('Page number'),
        per_page: z.number().optional().default(25).describe('Items per page'),
      },
      async ({ page, per_page }) => {
        try {
          const params: Record<string, string> = {
            page: String(page ?? 1),
            per_page: String(per_page ?? 25),
          };
          const data = await apiGet('/collaborators/', params);
          return createJsonResponse(data);
        } catch (error) {
          if (error instanceof APIError) {
            return createErrorResponse(error);
          }
          throw error;
        }
      }
    );
  • Zod schema defining the input parameters: page (optional, default 1) and per_page (optional, default 25).
    {
      page: z.number().optional().default(1).describe('Page number'),
      per_page: z.number().optional().default(25).describe('Items per page'),
    },
  • Where registerCollaborators is called to register the tool on the MCP server.
    // User management
    registerCollaborators(server);
  • The apiGet helper function used by the handler to make GET requests to the Storyblok Management API.
    export async function apiGet<T = unknown>(
      path: string,
      params: Record<string, string> = {}
    ): Promise<T> {
      const url = buildUrlWithParams(buildManagementUrl(path), params);
      const response = await fetch(url, {
        method: 'GET',
        headers: getManagementHeaders(),
      });
      return handleResponse<T>(response, url);
    }
Behavior3/5

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

The description discloses that the tool returns a 'paginated list', which informs the agent about the pagination behavior. However, with no annotations provided, it does not cover other behavioral aspects like required permissions, rate limits, or whether the operation is read-only. The pagination detail is valuable but not exhaustive.

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 sentence, under 20 words, and directly states the core function. It is front-loaded with the verb and resource, making it quickly scannable. Every word is necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity of the tool (2 parameters, no nested objects, no output schema), the description is adequate but not fully complete. It explains the paginated nature but does not describe the return format or fields. For a list retrieval tool, this is minimally acceptable.

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 input schema has 100% description coverage for both parameters (page and per_page), so the description adds little beyond the schema. It hints at pagination but does not provide further semantic context. Baseline 3 is appropriate 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 'Retrieves a paginated list of collaborators (users)' and specifies the scope 'in a specified Storyblok space'. This distinguishes it from sibling tools like add_collaborator and update_collaborator. However, the mention of 'specified space' is not reflected in the input schema, causing slight ambiguity.

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?

The description only states the tool's function without providing guidance on when to use it versus alternatives. It does not mention when not to use it or how it differs from other retrieval tools like retrieve_multiple_webhooks. This is the minimum viable for understanding its purpose.

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/hypescale/storyblok-mcp-server'

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