Skip to main content
Glama
AgentX-ai

Mailchimp MCP Server

by AgentX-ai

get_subscriber_activity

Retrieve subscriber activity data for automation emails in Mailchimp to monitor engagement and track email campaign performance.

Instructions

Get subscriber activity for an automation email

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflow_idYesThe workflow ID of the automation
email_idYesThe email ID within the automation
subscriber_hashYesThe subscriber hash

Implementation Reference

  • The handler function that executes the core logic of fetching subscriber activity from the Mailchimp API endpoint using the private makeRequest method.
    async getSubscriberActivity(
      workflowId: string,
      emailId: string,
      subscriberHash: string
    ): Promise<any> {
      return await this.makeRequest(
        `/automations/${workflowId}/emails/${emailId}/queue/${subscriberHash}/activity`
      );
    }
  • The input schema definition for the tool, specifying the required parameters and their descriptions.
    {
      name: "get_subscriber_activity",
      description: "Get subscriber activity for an automation email",
      inputSchema: {
        type: "object",
        properties: {
          workflow_id: {
            type: "string",
            description: "The workflow ID of the automation",
          },
          email_id: {
            type: "string",
            description: "The email ID within the automation",
          },
          subscriber_hash: {
            type: "string",
            description: "The subscriber hash",
          },
        },
        required: ["workflow_id", "email_id", "subscriber_hash"],
      },
    },
  • The registration and dispatch logic in the handleToolCall switch statement that calls the service handler and formats the response.
    case "get_subscriber_activity":
      const activity = await service.getSubscriberActivity(
        args.workflow_id,
        args.email_id,
        args.subscriber_hash
      );
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(activity, null, 2),
          },
        ],
      };
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. It only states what the tool does ('Get subscriber activity') without detailing traits like whether it's read-only, requires specific permissions, returns paginated data, or includes error handling. For a tool with three required parameters and no output schema, this lack of behavioral context is a significant gap.

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: 'Get subscriber activity for an automation email.' It is front-loaded with the core purpose, has zero wasted words, and is appropriately sized for the tool's complexity. Every part of the sentence earns its place by specifying the action and target.

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's complexity (three required parameters, no output schema, and no annotations), the description is incomplete. It lacks details on return values (e.g., activity types like opens or clicks), error conditions, or behavioral traits. While the schema covers parameters well, the overall context for effective tool use by an agent is insufficient.

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 clear parameter definitions (e.g., 'workflow_id' as 'The workflow ID of the automation'). The description adds no additional meaning beyond the schema, such as explaining relationships between parameters or usage examples. Given the high schema coverage, a baseline score of 3 is appropriate, as 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 tool's purpose: 'Get subscriber activity for an automation email.' It specifies the verb ('Get') and resource ('subscriber activity'), and while it doesn't explicitly differentiate from siblings like 'get_automation_email_report' or 'list_automation_subscribers,' the focus on individual subscriber activity is reasonably distinct. However, it lacks explicit sibling differentiation, preventing a score of 5.

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, context (e.g., after sending an automation email), or exclusions (e.g., not for bulk activity). With many sibling tools like 'get_automation_email_report' and 'list_automation_subscribers,' this omission leaves the agent guessing about appropriate usage scenarios.

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