Skip to main content
Glama
AgentX-ai

Mailchimp MCP Server

by AgentX-ai

get_campaign

Retrieve specific campaign details from Mailchimp to analyze email marketing performance and content.

Instructions

Get details of a specific campaign

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYesThe campaign ID

Implementation Reference

  • The handler function for the 'get_campaign' tool in handleToolCall. It invokes service.getCampaign with the provided campaign_id and returns the result as a JSON-formatted text response.
    case "get_campaign":
      const campaign = await service.getCampaign(args.campaign_id);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(campaign, null, 2),
          },
        ],
      };
  • The tool definition in getToolDefinitions, including name, description, and input schema that requires a 'campaign_id' string.
    {
      name: "get_campaign",
      description: "Get details of a specific campaign",
      inputSchema: {
        type: "object",
        properties: {
          campaign_id: {
            type: "string",
            description: "The campaign ID",
          },
        },
        required: ["campaign_id"],
      },
    },
  • The MailchimpService helper method getCampaign that makes an API request to retrieve campaign details from Mailchimp's /campaigns/{campaignId} endpoint.
    async getCampaign(campaignId: string): Promise<MailchimpCampaign> {
      return await this.makeRequest(`/campaigns/${campaignId}`);
    }
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 it 'gets details' but doesn't specify what details are returned, whether it's a read-only operation, if authentication is required, or any rate limits. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 with zero waste. It's appropriately sized for a simple retrieval tool and front-loads the essential information. Every word earns its place.

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 no annotations, no output schema, and a simple input schema, the description is incomplete. It doesn't explain what 'details' are returned, the response format, or any behavioral aspects. For a tool in a context with many siblings, more guidance would be helpful.

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?

Schema description coverage is 100%, so the schema fully documents the single parameter 'campaign_id'. The description adds no additional meaning about the parameter beyond what's in the schema, such as format examples or where to find campaign IDs. Baseline 3 is appropriate when 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 campaign', making the purpose unambiguous. It distinguishes from list_campaigns by specifying retrieval of a single campaign rather than listing multiple. However, it doesn't explicitly differentiate from get_campaign_report, which is a sibling tool.

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 get_campaign_report or list_campaigns. It doesn't mention prerequisites, context, or exclusions, leaving the agent to infer usage from the tool name alone.

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