Skip to main content
Glama
AgentX-ai

Mailchimp MCP Server

by AgentX-ai

get_account

Retrieve Mailchimp account details and configuration settings to manage email marketing campaigns and audience data.

Instructions

Get account information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Direct handler for the 'get_account' tool call in the handleToolCall function. Fetches account data using the Mailchimp service and returns it formatted as JSON text content for MCP.
    case "get_account":
      const account = await service.getAccount();
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(account, null, 2),
          },
        ],
      };
  • Tool registration definition including name, description, and empty input schema for 'get_account' in the exported tools list.
    {
      name: "get_account",
      description: "Get account information",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
  • Helper method in MailchimpService that performs the actual API request to retrieve account information from the Mailchimp root endpoint ('/').
    async getAccount(): Promise<MailchimpAccount> {
      return await this.makeRequest("/");
    }
  • Type definition for MailchimpAccount, used as the return type for getAccount and output schema reference.
    export interface MailchimpAccount {
      account_id: string;
      account_name: string;
      account_industry: string;
      account_created: string;
      account_updated: string;
      contact: {
        company: string;
        address1: string;
        address2: string;
        city: string;
        state: string;
        zip: string;
        country: string;
        phone: string;
      };
      pro_enabled: boolean;
      last_login: string;
      total_subscribers: number;
      industry_stats: {
        type: string;
        open_rate: number;
        click_rate: number;
        bounce_rate: number;
        unopen_rate: number;
        unsub_rate: number;
        abuse_rate: number;
      };
      _links?: Array<{
        rel: string;
        href: string;
        method: string;
        targetSchema?: string;
        schema?: string;
      }>;
    }
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. 'Get account information' implies a read operation, but it doesn't specify whether this requires authentication, what permissions are needed, whether it returns personal or organizational data, or if there are rate limits. The description provides minimal behavioral context beyond the basic read implication.

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 with just three words: 'Get account information'. It's front-loaded and wastes no words, making it easy to parse. Every word contributes to the core meaning without unnecessary elaboration.

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 lack of annotations and output schema, the description is incomplete for a tool that presumably retrieves account data. It doesn't explain what 'account information' includes, the format of the return value, or any behavioral constraints. For a tool with no structured metadata, the description should provide more context about what is retrieved and how it behaves.

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?

The input schema has 0 parameters with 100% coverage, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately doesn't mention any. Since there are no parameters, the baseline score is 4, as the description doesn't create confusion about parameters.

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

Purpose2/5

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

The description 'Get account information' is a tautology that essentially restates the tool name 'get_account'. While it indicates a retrieval action, it doesn't specify what kind of account information is retrieved or distinguish this tool from sibling tools like 'get_member' or 'get_subscriber_activity' which might also retrieve account-related data. The purpose is vague and lacks specificity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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. There are multiple sibling tools that might retrieve account-related information (e.g., 'get_member', 'get_subscriber_activity'), but the description doesn't clarify the scope or context for using 'get_account'. No prerequisites, exclusions, or alternatives are mentioned.

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