Skip to main content
Glama

list_tools

List all available tool categories and their counts, providing a module-level summary of Storyblok Management API tools.

Instructions

Lists all available tool categories with their tool counts. Returns module-level summary of 130 Storyblok Management API tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The registerMeta function registers the 'list_tools' tool handler with the MCP server. It calls server.tool('list_tools', ...) and the handler returns a hardcoded list of all 30 tool modules with their tool counts and descriptions.
    export function registerMeta(server: McpServer): void {
      server.tool(
        'list_tools',
        'Lists all available tool categories with their tool counts. Returns module-level summary of 130 Storyblok Management API tools.',
        {},
        async () => {
          try {
            const modules = [
              { name: 'ping', tools: 1, description: 'Server health check' },
              { name: 'meta', tools: 1, description: 'Tool discovery' },
              { name: 'tags', tools: 5, description: 'Tag management' },
              { name: 'internal-tags', tools: 4, description: 'Internal tag management' },
              { name: 'access-tokens', tools: 4, description: 'Access token management' },
              { name: 'activities', tools: 2, description: 'Activity tracking' },
              { name: 'approvals', tools: 5, description: 'Approval workflows' },
              { name: 'branch-deployments', tools: 1, description: 'Branch deployment status' },
              { name: 'collaborators', tools: 4, description: 'Collaborator management' },
              { name: 'data-sources', tools: 5, description: 'Datasource management' },
              { name: 'datasource-entries', tools: 5, description: 'Datasource entry management' },
              { name: 'pipelines', tools: 5, description: 'Branch/pipeline management' },
              { name: 'presets', tools: 5, description: 'Preset management' },
              { name: 'releases', tools: 5, description: 'Release management' },
              { name: 'scheduling-stories', tools: 5, description: 'Story scheduling' },
              { name: 'space', tools: 7, description: 'Space management' },
              { name: 'space-roles', tools: 5, description: 'Space role management' },
              { name: 'tasks', tools: 5, description: 'Task management' },
              { name: 'webhooks', tools: 5, description: 'Webhook management' },
              { name: 'workflows', tools: 6, description: 'Workflow management' },
              { name: 'workflow-stage', tools: 5, description: 'Workflow stage management' },
              { name: 'workflow-stage-changes', tools: 2, description: 'Workflow stage changes' },
              { name: 'components', tools: 9, description: 'Component management' },
              { name: 'components-folder', tools: 5, description: 'Component folder management' },
              { name: 'assets', tools: 9, description: 'Asset management' },
              { name: 'assets-folder', tools: 5, description: 'Asset folder management' },
              { name: 'stories', tools: 18, description: 'Story CRUD and bulk operations' },
              { name: 'discussions', tools: 10, description: 'Discussion and comment management' },
              { name: 'extensions', tools: 7, description: 'Extension management' },
              { name: 'field-plugins', tools: 5, description: 'Field plugin management' },
            ];
    
            const totalTools = modules.reduce((sum, m) => sum + m.tools, 0);
            const formatted = modules.map(
              (m) => `${m.name} (${m.tools} tools): ${m.description}`
            );
    
            return {
              content: [
                {
                  type: 'text' as const,
                  text: `Storyblok MCP Server - ${totalTools} tools across ${modules.length} modules:\n\n${formatted.join('\n')}`,
                },
              ],
              total_tools: totalTools,
              total_modules: modules.length,
            };
          } catch (error) {
            return createErrorResponse(error);
          }
        }
  • src/tools/meta.ts:8-67 (registration)
    The 'list_tools' tool is registered via server.tool() inside the registerMeta function. The registration includes an empty schema object {} (no input parameters) and a description string.
    export function registerMeta(server: McpServer): void {
      server.tool(
        'list_tools',
        'Lists all available tool categories with their tool counts. Returns module-level summary of 130 Storyblok Management API tools.',
        {},
        async () => {
          try {
            const modules = [
              { name: 'ping', tools: 1, description: 'Server health check' },
              { name: 'meta', tools: 1, description: 'Tool discovery' },
              { name: 'tags', tools: 5, description: 'Tag management' },
              { name: 'internal-tags', tools: 4, description: 'Internal tag management' },
              { name: 'access-tokens', tools: 4, description: 'Access token management' },
              { name: 'activities', tools: 2, description: 'Activity tracking' },
              { name: 'approvals', tools: 5, description: 'Approval workflows' },
              { name: 'branch-deployments', tools: 1, description: 'Branch deployment status' },
              { name: 'collaborators', tools: 4, description: 'Collaborator management' },
              { name: 'data-sources', tools: 5, description: 'Datasource management' },
              { name: 'datasource-entries', tools: 5, description: 'Datasource entry management' },
              { name: 'pipelines', tools: 5, description: 'Branch/pipeline management' },
              { name: 'presets', tools: 5, description: 'Preset management' },
              { name: 'releases', tools: 5, description: 'Release management' },
              { name: 'scheduling-stories', tools: 5, description: 'Story scheduling' },
              { name: 'space', tools: 7, description: 'Space management' },
              { name: 'space-roles', tools: 5, description: 'Space role management' },
              { name: 'tasks', tools: 5, description: 'Task management' },
              { name: 'webhooks', tools: 5, description: 'Webhook management' },
              { name: 'workflows', tools: 6, description: 'Workflow management' },
              { name: 'workflow-stage', tools: 5, description: 'Workflow stage management' },
              { name: 'workflow-stage-changes', tools: 2, description: 'Workflow stage changes' },
              { name: 'components', tools: 9, description: 'Component management' },
              { name: 'components-folder', tools: 5, description: 'Component folder management' },
              { name: 'assets', tools: 9, description: 'Asset management' },
              { name: 'assets-folder', tools: 5, description: 'Asset folder management' },
              { name: 'stories', tools: 18, description: 'Story CRUD and bulk operations' },
              { name: 'discussions', tools: 10, description: 'Discussion and comment management' },
              { name: 'extensions', tools: 7, description: 'Extension management' },
              { name: 'field-plugins', tools: 5, description: 'Field plugin management' },
            ];
    
            const totalTools = modules.reduce((sum, m) => sum + m.tools, 0);
            const formatted = modules.map(
              (m) => `${m.name} (${m.tools} tools): ${m.description}`
            );
    
            return {
              content: [
                {
                  type: 'text' as const,
                  text: `Storyblok MCP Server - ${totalTools} tools across ${modules.length} modules:\n\n${formatted.join('\n')}`,
                },
              ],
              total_tools: totalTools,
              total_modules: modules.length,
            };
          } catch (error) {
            return createErrorResponse(error);
          }
        }
      );
  • The input schema for 'list_tools' is an empty object {} — the tool takes no input parameters.
    {},
  • The createErrorResponse helper is used by the list_tools handler to format error responses in case of exceptions.
    export function createErrorResponse(
      error: unknown,
      errorCode?: string
    ): McpErrorResponse {
      const message = error instanceof Error ? error.message : String(error);
      const response: McpErrorResponse = {
        isError: true,
        content: [{ type: 'text', text: message }],
      };
    
      if (errorCode) {
        response.errorCode = errorCode;
        response.errorMessage = message;
      }
    
      return response;
    }
  • registerMeta(server) is called inside registerAllTools, which is the central tool registration entrypoint.
    export function registerAllTools(server: McpServer): void {
      // Simple tools
      registerPing(server);
      registerMeta(server);
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states what the tool returns but does not disclose any behavioral traits such as side effects, authentication needs, or rate limits.

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 two sentences, front-loaded with the key action, and contains no unnecessary words. It is efficiently structured.

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

Completeness4/5

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

For a simple tool with no parameters, the description is mostly complete. It clearly states the output. However, it could be slightly improved by mentioning if the list is global or per-space, but given the tool's simplicity, it is adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has no parameters, so the description does not need to add parameter meaning. However, it does add context by stating the return value (tool categories with counts and module-level summary), which is useful beyond the empty 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 what the tool does: lists tool categories with counts, and specifies the scope (130 Storyblok Management API tools). It is specific and distinguishes itself from sibling tools that operate on individual entities.

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 no guidance on when to use this tool versus alternatives. It does not mention any context of use, prerequisites, or when not to use it.

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