Skip to main content
Glama

delete_space_role

Delete a space role in Storyblok by specifying its ID to manage user permissions within a space.

Instructions

Deletes a space role using the Storyblok Management API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
space_role_idYesID of the space role to delete

Implementation Reference

  • The handler function for the 'delete_space_role' tool. It registers a tool with the MCP server that accepts a 'space_role_id' number, calls apiDelete to the Storyblok Management API endpoint '/space_roles/{id}', and returns a success message or an error response.
    // Tool: delete_space_role
    server.tool(
      'delete_space_role',
      'Deletes a space role using the Storyblok Management API.',
      {
        space_role_id: z.number().describe('ID of the space role to delete'),
      },
      async ({ space_role_id }) => {
        try {
          await apiDelete(`/space_roles/${space_role_id}`);
          return {
            content: [
              {
                type: 'text' as const,
                text: `Space role ${space_role_id} has been successfully deleted.`,
              },
            ],
          };
        } catch (error) {
          if (error instanceof APIError) {
            return createErrorResponse(error);
          }
          throw error;
        }
      }
    );
  • Input schema for delete_space_role: requires a single 'space_role_id' field of type number, described as 'ID of the space role to delete'.
    {
      space_role_id: z.number().describe('ID of the space role to delete'),
    },
  • Registration call: registerSpaceRoles(server) is invoked from the central tools index, which registers all space role tools including delete_space_role.
    registerSpaceRoles(server);
Behavior2/5

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

No annotations provided, and description fails to disclose behavioral traits such as idempotency, effects, or permission requirements.

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?

Extremely concise single sentence with no unnecessary words.

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?

Simple tool with one parameter, but missing details like error handling, idempotency, or return behavior.

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 covers the only parameter fully (100% coverage), and description adds no additional meaning beyond 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?

Description uses specific verb 'Deletes' and resource 'space role', clearly distinguishing from sibling tools like get_space_role or update_space_role.

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?

No guidance on when to use this tool vs alternatives, no prerequisites or context provided.

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