Skip to main content
Glama
microcmsio

microCMS MCP Server

by microcmsio

microcms_get_api_list

Retrieve all available API endpoints from microCMS Management API, including names, endpoints, and types (list/object) for content management operations.

Instructions

Get list of all available APIs (endpoints) from microCMS Management API. Returns API name, endpoint, and type (list/object) for each API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'microcms_get_api_list' tool, which calls the underlying getApiList function from the client module.
    export async function handleGetApiList(params: ToolParameters) {
      return await getApiList();
    }
  • Tool definition including name, description, and input schema (empty object, no parameters required). This is used for registration and validation.
    export const getApiListTool: Tool = {
      name: 'microcms_get_api_list',
      description: 'Get list of all available APIs (endpoints) from microCMS Management API. Returns API name, endpoint, and type (list/object) for each API.',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    };
  • src/server.ts:47-72 (registration)
    Registration of the tool in the MCP server's listTools handler, where getApiListTool is included in the array of available tools.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: [
          getListTool,
          getListMetaTool,
          getContentTool,
          getContentMetaTool,
          createContentPublishedTool,
          createContentDraftTool,
          createContentsBulkPublishedTool,
          createContentsBulkDraftTool,
          updateContentPublishedTool,
          updateContentDraftTool,
          patchContentTool,
          patchContentStatusTool,
          patchContentCreatedByTool,
          deleteContentTool,
          getMediaTool,
          uploadMediaTool,
          deleteMediaTool,
          getApiInfoTool,
          getApiListTool,
          getMemberTool,
        ],
      };
    });
  • src/server.ts:136-138 (registration)
    Dispatch registration in the CallToolRequestSchema handler's switch statement, mapping the tool name to its handler function.
    case 'microcms_get_api_list':
      result = await handleGetApiList(params);
      break;
  • Core helper function that performs the actual API call to retrieve the list of APIs from microCMS Management API.
    export async function getApiList(): Promise<any> {
      const url = `https://${config.serviceDomain}.microcms-management.io/api/v1/apis`;
    
      const response = await fetch(url, {
        method: 'GET',
        headers: {
          'X-MICROCMS-API-KEY': config.apiKey,
        },
      });
    
      if (!response.ok) {
        const errorText = await response.text();
        throw new Error(`Failed to get API list: ${response.status} ${response.statusText} - ${errorText}`);
      }
    
      return await response.json();
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses that this is a read operation ('Get list') and describes the return format, but lacks details on permissions, rate limits, error handling, or pagination. For a tool with zero annotation coverage, this is adequate but minimal.

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, well-structured sentence that efficiently conveys the action, resource, and return data. Every word adds value, with no wasted text, making it highly concise and front-loaded.

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 tool's low complexity (0 parameters, no output schema, no annotations), the description is complete enough to understand its basic function. However, it could be more robust by addressing potential behavioral aspects like authentication needs or response structure, which are missing but not critical for this simple tool.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately focuses on the tool's purpose and output without redundant parameter details, earning a baseline score above 3 for efficient compensation.

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 the specific action ('Get list'), the resource ('all available APIs (endpoints) from microCMS Management API'), and the return data ('API name, endpoint, and type'). It distinguishes this from sibling tools like microcms_get_api_info by focusing on listing all APIs rather than getting details of a specific one.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context by specifying it retrieves 'all available APIs' from the Management API, suggesting it's for discovery or overview purposes. However, it doesn't explicitly state when to use this versus alternatives like microcms_get_api_info or provide exclusions, leaving some guidance gaps.

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/microcmsio/microcms-mcp-server'

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