Skip to main content
Glama
microcmsio

microCMS MCP Server

by microcmsio

microcms_get_member

Retrieve specific member details including ID, name, email, and MFA status from the microCMS Management API 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
memberIdYesMember ID to retrieve

Implementation Reference

  • The handler function for the 'microcms_get_member' tool. It extracts the memberId from parameters and delegates to the client-side getMember function.
    export async function handleGetMember(params: ToolParameters & { memberId: string }) {
      const { memberId } = params;
    
      return await getMember(memberId);
    }
  • Tool definition object including the name, description, and input schema that validates the required 'memberId' parameter.
    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: {
          memberId: {
            type: 'string',
            description: 'Member ID to retrieve',
          },
        },
        required: ['memberId'],
      },
    };
  • src/server.ts:139-141 (registration)
    Tool handler registration in the server's CallToolRequest switch statement, routing 'microcms_get_member' calls to handleGetMember.
    case 'microcms_get_member':
      result = await handleGetMember(params as ToolParameters & { memberId: string });
      break;
  • src/server.ts:47-72 (registration)
    Server registration of available tools list, including getMemberTool for 'microcms_get_member'.
    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,
        ],
      };
    });
  • Core helper function that performs the actual HTTP fetch to retrieve member details from the microCMS Management API.
    export async function getMember(memberId: string): Promise<any> {
      const url = `https://${config.serviceDomain}.microcms-management.io/api/v1/members/${memberId}`;
    
      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 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 provided, the description carries the full burden of behavioral disclosure. It mentions the return information (ID, name, email, MFA status), which is helpful, but lacks details on error handling, rate limits, authentication requirements, or whether it's a read-only operation. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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, efficient sentence that front-loads the purpose and includes key return details. Every word earns its place, with no wasted text, making it highly concise and well-structured.

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 (single parameter, no output schema, no annotations), the description is adequate but incomplete. It covers the basic purpose and return values, but lacks context on usage guidelines and behavioral traits, making it minimally viable for a simple read operation.

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 single parameter 'memberId' documented as 'Member ID to retrieve'. The description doesn't add any meaning beyond this, such as format examples or constraints, so it meets the baseline of 3 where the schema does the heavy lifting.

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 verb 'Get' and the resource 'a specific member from microCMS Management API', which is specific and unambiguous. It distinguishes from siblings like 'microcms_get_content' or 'microcms_get_list' by focusing on members rather than content or lists, though it doesn't explicitly contrast them.

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 doesn't mention prerequisites (e.g., authentication), when not to use it, or compare it to sibling tools like 'microcms_get_content' for different resource types, leaving usage context implied at best.

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