Skip to main content
Glama
AgentX-ai

Mailchimp MCP Server

by AgentX-ai

get_member

Retrieve detailed information about a specific subscriber from a Mailchimp email list using list ID and subscriber hash.

Instructions

Get details of a specific member

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYesThe list ID
subscriber_hashYesThe subscriber hash

Implementation Reference

  • Core handler function in MailchimpService that makes the API request to retrieve member details using the list ID and subscriber hash.
    async getMember(
      listId: string,
      subscriberHash: string
    ): Promise<MailchimpMember> {
      return await this.makeRequest(`/lists/${listId}/members/${subscriberHash}`);
    }
  • Input schema and tool definition for the 'get_member' tool, specifying required parameters list_id and subscriber_hash.
    {
      name: "get_member",
      description: "Get details of a specific member",
      inputSchema: {
        type: "object",
        properties: {
          list_id: {
            type: "string",
            description: "The list ID",
          },
          subscriber_hash: {
            type: "string",
            description: "The subscriber hash",
          },
        },
        required: ["list_id", "subscriber_hash"],
      },
    },
  • Registration of the 'get_member' tool in the getToolDefinitions array.
    {
      name: "get_member",
      description: "Get details of a specific member",
      inputSchema: {
        type: "object",
        properties: {
          list_id: {
            type: "string",
            description: "The list ID",
          },
          subscriber_hash: {
            type: "string",
            description: "The subscriber hash",
          },
        },
        required: ["list_id", "subscriber_hash"],
      },
    },
  • Tool call handler in handleToolCall function that invokes the service.getMember method and returns formatted JSON response.
    case "get_member":
      const member = await service.getMember(
        args.list_id,
        args.subscriber_hash
      );
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(member, null, 2),
          },
        ],
      };
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 but offers minimal information. It doesn't specify whether this is a read-only operation, what authentication is required, potential rate limits, error conditions, or what format/details are returned. For a tool with 2 required parameters and no output schema, this leaves significant behavioral gaps.

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 extremely concise at just 6 words, front-loading the core purpose without any unnecessary elaboration. Every word earns its place, making it efficient for quick understanding while avoiding verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 2 required parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what a 'member' represents in this context, what details are returned, or how this operation differs from other member-related tools. For a retrieval operation with specific identifiers needed, more context is warranted.

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 schema has 100% description coverage, with both parameters clearly documented as 'list_id' and 'subscriber_hash'. The description doesn't add any additional meaning beyond what the schema provides, such as explaining what constitutes a 'member' or how these parameters relate to each other. Baseline 3 is appropriate when 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 resource ('details of a specific member'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'list_members' or 'get_subscriber_activity', which would require more specificity about what distinguishes this particular member retrieval operation.

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 like 'list_members' or other 'get_' tools. There's no mention of prerequisites, context requirements, or distinctions from similar operations, leaving the agent without usage direction.

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/AgentX-ai/mailchimp-mcp'

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