Skip to main content
Glama

retrieve_multiple_access_tokens

Retrieve all access tokens for the current Storyblok space via the Management API. Get a complete list of tokens without parameters.

Instructions

Retrieve all access tokens for the current Storyblok space using the Management API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'retrieve_multiple_access_tokens' tool handler. It calls apiGet('/api_keys/') to fetch all access tokens for the current Storyblok space, returning JSON-formatted results. Registered via server.tool() with an empty schema (no input parameters).
    // Tool: retrieve_multiple_access_tokens
    server.tool(
      'retrieve_multiple_access_tokens',
      'Retrieve all access tokens for the current Storyblok space using the Management API.',
      {},
      async () => {
        try {
          const data = await apiGet('/api_keys/');
          return createJsonResponse(data);
        } catch (error) {
          if (error instanceof APIError) {
            return createErrorResponse(error);
          }
          throw error;
        }
      }
    );
  • The input schema for 'retrieve_multiple_access_tokens' is an empty object {}, meaning the tool takes no parameters.
    {},
  • Registration of 'retrieve_multiple_access_tokens' within the registerAccessTokens function, which is exported and called from src/tools/index.ts.
    export function registerAccessTokens(server: McpServer): void {
      // Tool: retrieve_multiple_access_tokens
      server.tool(
        'retrieve_multiple_access_tokens',
        'Retrieve all access tokens for the current Storyblok space using the Management API.',
        {},
        async () => {
          try {
            const data = await apiGet('/api_keys/');
            return createJsonResponse(data);
          } catch (error) {
            if (error instanceof APIError) {
              return createErrorResponse(error);
            }
            throw error;
          }
        }
      );
  • Import of registerAccessTokens from the access-tokens module.
    import { registerAccessTokens } from './access-tokens.js';
  • Call to registerAccessTokens(server) to register all access token tools including retrieve_multiple_access_tokens.
    registerAccessTokens(server);
Behavior4/5

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

No annotations provided. Description implies a read-only retrieval operation, which is clear. However, does not explicitly state read-only, authentication needs, or any restrictions. Missing minor details for full transparency.

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?

Single sentence, no wasted words. Information is front-loaded and achieves the goal efficiently.

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?

Description is sufficient for a retrieval tool with no output schema, but could mention that it returns a list of tokens. Considering the simplicity, it is nearly complete.

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

Parameters5/5

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

Input schema has zero parameters, which are fully covered. Description adds valuable context about scope and API, exceeding baseline expectations for a no-parameter tool.

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 clearly states verb (retrieve), resource (all access tokens), scope (current Storyblok space), and API (Management API). It distinguishes from siblings like create/delete/update access tokens.

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?

No explicit guidance on when to use this tool over alternatives, e.g., whether to use retrieve_multiple_access_tokens vs others like retrieve_multiple_presets. Usage is implied by the name, but no 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