Skip to main content
Glama
AgentX-ai

Mailchimp MCP Server

by AgentX-ai

get_merge_field

Retrieve specific merge field details from a Mailchimp list using list ID and merge field ID for email marketing data management.

Instructions

Get details of a specific merge field

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYesThe list ID
merge_field_idYesThe merge field ID

Implementation Reference

  • Core handler function in MailchimpService that executes the API call to retrieve a specific merge field by list ID and merge field ID.
    async getMergeField(
      listId: string,
      mergeFieldId: number
    ): Promise<MailchimpMergeField> {
      return await this.makeRequest(
        `/lists/${listId}/merge-fields/${mergeFieldId}`
      );
    }
  • Tool dispatch handler in handleToolCall that calls the service method and returns formatted JSON response.
    case "get_merge_field":
      const mergeField = await service.getMergeField(
        args.list_id,
        args.merge_field_id
      );
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(mergeField, null, 2),
          },
        ],
      };
  • Tool registration including name, description, and input schema definition in getToolDefinitions.
      name: "get_merge_field",
      description: "Get details of a specific merge field",
      inputSchema: {
        type: "object",
        properties: {
          list_id: {
            type: "string",
            description: "The list ID",
          },
          merge_field_id: {
            type: "number",
            description: "The merge field ID",
          },
        },
        required: ["list_id", "merge_field_id"],
      },
    },
  • Input schema for the get_merge_field tool.
      name: "get_merge_field",
      description: "Get details of a specific merge field",
      inputSchema: {
        type: "object",
        properties: {
          list_id: {
            type: "string",
            description: "The list ID",
          },
          merge_field_id: {
            type: "number",
            description: "The merge field ID",
          },
        },
        required: ["list_id", "merge_field_id"],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a 'Get' operation which implies read-only behavior, but doesn't clarify authentication requirements, rate limits, error conditions, or what format/details are returned. For a tool with zero annotation coverage, this is insufficient.

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 gets straight to the point with no wasted words. It's appropriately sized for a simple retrieval tool and front-loads the essential 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?

For a simple read operation with 2 required parameters and no output schema, the description is minimally adequate but leaves important gaps. It doesn't explain what 'details' are returned, error handling, or how this differs from the list_merge_fields sibling tool. The absence of annotations means more behavioral context should be provided.

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 description doesn't add any parameter information beyond what's already in the schema (which has 100% coverage). It doesn't explain the relationship between list_id and merge_field_id, or provide examples of valid values. With complete schema coverage, the baseline score of 3 is appropriate.

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 action ('Get details') and resource ('specific merge field'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'list_merge_fields' which would list multiple merge fields rather than retrieve 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 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 the sibling 'list_merge_fields' tool for listing multiple merge fields, nor does it explain prerequisites like needing to know both list_id and merge_field_id before calling this tool.

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