Skip to main content
Glama

delete_collaborator

Delete a collaborator from a Storyblok space using their collaborator ID or SSO ID.

Instructions

Deletes a collaborator from a specified Storyblok space. Can delete by collaborator_id or sso_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collaborator_idYesID of the collaborator to delete
sso_idNoSSO ID for SSO users (alternative to collaborator_id)

Implementation Reference

  • The 'delete_collaborator' tool handler. Registers an MCP tool that accepts collaborator_id (number) or sso_id (string) and calls the API DELETE endpoint /collaborators/{identifier}. Returns JSON response on success or an error response if an APIError occurs.
    // Tool: delete_collaborator
    server.tool(
      'delete_collaborator',
      'Deletes a collaborator from a specified Storyblok space. Can delete by collaborator_id or sso_id.',
      {
        collaborator_id: z.number().describe('ID of the collaborator to delete'),
        sso_id: z.string().optional().describe('SSO ID for SSO users (alternative to collaborator_id)'),
      },
      async ({ collaborator_id, sso_id }) => {
        try {
          const identifier = sso_id ?? collaborator_id;
          const data = await apiDelete(`/collaborators/${identifier}`);
          return createJsonResponse(data);
        } catch (error) {
          if (error instanceof APIError) {
            return createErrorResponse(error);
          }
          throw error;
        }
      }
    );
  • Input schema for delete_collaborator: collaborator_id (required number) with description, and sso_id (optional string) as an alternative identifier for SSO users.
    {
      collaborator_id: z.number().describe('ID of the collaborator to delete'),
      sso_id: z.string().optional().describe('SSO ID for SSO users (alternative to collaborator_id)'),
    },
  • Import of registerCollaborators from ./collaborators.js, which includes the delete_collaborator tool registration.
    import { registerCollaborators } from './collaborators.js';
  • Invocation of registerCollaborators(server) inside registerAllTools, registering the delete_collaborator tool.
    registerCollaborators(server);
  • The apiDelete helper function used by the handler to make the DELETE HTTP request to the Storyblok Management API.
    export async function apiDelete<T = unknown>(path: string): Promise<T> {
      const url = buildManagementUrl(path);
      const response = await fetch(url, {
        method: 'DELETE',
        headers: getManagementHeaders(),
      });
      return handleResponse<T>(response, url);
    }
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions the deletion action but omits critical details such as irreversibility, cascading effects on permissions, or error handling. For a destructive operation, this is insufficient transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no filler. However, the phrase 'specified Storyblok space' is ambiguous because the input schema does not include a space identifier, which could confuse the agent.

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 destructive nature and lack of output schema, the description should explain what happens after deletion, space identification context, and any constraints. It fails to mention return values, side effects, or how the space is determined, leaving the agent with an incomplete picture.

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%, so the baseline is 3. The description adds that deletion can be performed by either collaborator_id or sso_id, but this is already stated in the schema's property descriptions. Thus, minimal value is added beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Deletes a collaborator from a specified Storyblok space', which provides a specific verb (deletes) and resource (collaborator). This effectively distinguishes the tool from siblings like add_collaborator and update_collaborator.

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 implies when to use this tool (to remove a collaborator), but lacks explicit guidance on prerequisites, permissions, or when not to use it. No exclusionary context is provided, leaving the agent to infer usage from the tool name alone.

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