Skip to main content
Glama
microcmsio

microCMS MCP Server

by microcmsio

microcms_get_member

Retrieve a specific member's details from microCMS Management API, including ID, name, email, and MFA status, using the member ID.

Instructions

Get a specific member from microCMS Management API. Returns member information including ID, name, email, and MFA status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serviceIdNoService ID (required in multi-service mode, optional in single-service mode)
memberIdYesMember ID to retrieve

Implementation Reference

  • The handler function 'handleGetMember' that executes the 'microcms_get_member' tool logic. It extracts the memberId from params and calls the 'getMember' client function.
    export async function handleGetMember(
      params: ToolParameters & { memberId: string },
      serviceId?: string
    ) {
      const { memberId } = params;
    
      return await getMember(memberId, serviceId);
    }
  • The tool definition/schema for 'microcms_get_member' including inputSchema requiring memberId and optional serviceId.
    export const getMemberTool: Tool = {
      name: 'microcms_get_member',
      description:
        'Get a specific member from microCMS Management API. Returns member information including ID, name, email, and MFA status.',
      inputSchema: {
        type: 'object',
        properties: {
          serviceId: {
            type: 'string',
            description:
              'Service ID (required in multi-service mode, optional in single-service mode)',
          },
          memberId: {
            type: 'string',
            description: 'Member ID to retrieve',
          },
        },
        required: ['memberId'],
      },
    };
  • src/server.ts:89-89 (registration)
    Registration of getMemberTool in the tools array (line 89).
    getMemberTool,
  • src/server.ts:130-130 (registration)
    Registration of handleGetMember in the toolHandlers map under key 'microcms_get_member' (line 130).
    microcms_get_member: handleGetMember,
  • The helper function 'getMember' that makes the actual HTTP GET request to the microCMS Management API endpoint /api/v1/members/{memberId}.
    export async function getMember(
      memberId: string,
      serviceId?: string
    ): Promise<MemberInfo> {
      const clients = getClientsForService(serviceId);
      const url = `https://${clients.serviceDomain}.microcms-management.io/api/v1/members/${memberId}`;
    
      const response = await fetch(url, {
        method: 'GET',
        headers: {
          'X-MICROCMS-API-KEY': clients.apiKey,
        },
      });
    
      if (!response.ok) {
        const errorText = await response.text();
        throw new Error(
          `Failed to get member: ${response.status} ${response.statusText} - ${errorText}`
        );
      }
    
      return await response.json();
    }
Behavior2/5

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

With no annotations, the description carries full behavioral disclosure burden. It only states what the tool returns, but fails to mention authentication needs, rate limits, or any side effects. The tool is a read operation but does not confirm idempotency or safety.

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 sentence plus a bullet-like list of return fields. It is highly concise, front-loaded, and contains no redundant information.

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?

The description lists some return fields but does not fully specify the output structure (e.g., data types, nested objects). Since there is no output schema, more detail would be helpful. Still, it provides sufficient context for a simple retrieval 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?

Schema coverage is 100% with descriptions for both parameters. The description adds value by listing expected return fields (ID, name, email, MFA status), which are not in the schema. This helps the agent understand the output beyond parameter input.

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 verb 'Get', the resource 'member', and lists specific return fields (ID, name, email, MFA status). It distinguishes itself from sibling tools like 'get_content' or 'get_api_info' by targeting a member.

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 is provided on when to use this tool versus alternatives. The description does not mention prerequisites, exclusions, or compare to other tools like 'get_services' or 'get_content'.

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