Skip to main content
Glama
microcmsio

microCMS MCP Server

by microcmsio

microcms_get_api_info

Retrieve API schema information from microCMS Management API to understand content structure and field relationships, including referenced endpoints in relation fields.

Instructions

Get API schema information from microCMS Management API. In relation and relationList field, you can get its schema using referencedApiEndpoint and microcms_get_api_info tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endpointYesContent type name to get schema info (e.g., "blogs", "news")

Implementation Reference

  • Core implementation of fetching API schema information from microCMS Management API using the management endpoint.
    export async function getApiInfo(endpoint: string): Promise<any> {
      const url = `https://${config.serviceDomain}.microcms-management.io/api/v1/apis/${endpoint}`;
    
      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 info: ${response.status} ${response.statusText} - ${errorText}`);
      }
    
      return await response.json();
    }
  • Tool definition including input schema for the microcms_get_api_info tool.
    export const getApiInfoTool: Tool = {
      name: 'microcms_get_api_info',
      description: 'Get API schema information from microCMS Management API. In relation and relationList field, you can get its schema using referencedApiEndpoint and microcms_get_api_info tool.',
      inputSchema: {
        type: 'object',
        properties: {
          endpoint: {
            type: 'string',
            description: 'Content type name to get schema info (e.g., "blogs", "news")',
          },
        },
        required: ['endpoint'],
      },
    };
  • Tool-specific handler that extracts the endpoint parameter and delegates to the core getApiInfo function.
    export async function handleGetApiInfo(params: ToolParameters) {
      const { endpoint } = params;
    
      return await getApiInfo(endpoint);
    }
  • src/server.ts:133-135 (registration)
    Dispatch case in the server tool caller that invokes the tool handler.
    case 'microcms_get_api_info':
      result = await handleGetApiInfo(params);
      break;
  • src/server.ts:67-67 (registration)
    Registration of the tool in the listTools response.
    getApiInfoTool,
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 of behavioral disclosure. It states the tool retrieves schema information but doesn't mention whether it's a read-only operation, requires specific permissions, has rate limits, or what the response format looks like. The description adds minimal behavioral context beyond the basic purpose, leaving gaps for a tool that interacts with an API management system.

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?

The description is concise and front-loaded, with the first sentence stating the core purpose clearly. The second sentence adds useful context about usage with relation fields, which earns its place by providing additional guidance. There's no unnecessary verbosity or repetition, making it efficient for an agent to parse.

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 moderate complexity (retrieving schema info from an API), lack of annotations, and no output schema, the description is minimally adequate. It explains what the tool does and hints at usage but lacks details on behavioral aspects like safety, permissions, or response structure. For a tool in a management API context, more completeness would be beneficial, but it meets the basic threshold for understanding its role among siblings.

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?

The input schema has 100% description coverage, with the 'endpoint' parameter clearly documented as 'Content type name to get schema info (e.g., "blogs", "news").' The description doesn't add any parameter-specific details beyond what the schema provides, such as examples or constraints. Given the high schema coverage, a baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't need to given the schema's completeness.

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

Purpose4/5

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

The description clearly states the tool's purpose: 'Get API schema information from microCMS Management API.' It specifies the verb ('Get') and resource ('API schema information'), and distinguishes it from content-focused siblings by focusing on schema metadata rather than content operations. However, it doesn't explicitly differentiate from microcms_get_api_list, which likely lists APIs rather than getting schema details for a specific endpoint.

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 provides implied usage guidance by mentioning 'In relation and relationList field, you can get its schema using referencedApiEndpoint and microcms_get_api_info tool,' suggesting it's useful for resolving referenced schemas. However, it lacks explicit when-to-use vs. when-not-to-use instructions or clear alternatives among siblings like microcms_get_api_list, leaving the agent to infer context from the tool name and description.

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