Skip to main content
Glama

schedule_campaign

Schedule email campaigns for automated delivery at specified times using the Mailchimp Marketing API. Set campaign_id and schedule_time in ISO 8601 UTC format to plan future email sends.

Instructions

Schedule a campaign. schedule_time must be ISO 8601 UTC (e.g. '2026-04-01T14:00:00+00:00').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYes
schedule_timeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The schedule_campaign tool handler, which uses the Mailchimp API client to POST to the /campaigns/{campaign_id}/actions/schedule endpoint.
    async def schedule_campaign(campaign_id: str, schedule_time: str) -> str:
        """Schedule a campaign. schedule_time must be ISO 8601 UTC (e.g. '2026-04-01T14:00:00+00:00')."""
        mc = get_client()
        await mc.post(
            f"/campaigns/{campaign_id}/actions/schedule",
            json={"schedule_time": schedule_time},
        )
        return _fmt({
            "campaign_id": campaign_id,
            "scheduled_for": schedule_time,
            "message": "Campaign scheduled.",
        })
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. It mentions the required format for 'schedule_time' but doesn't cover critical aspects like permissions needed, whether scheduling is reversible, error handling, or rate limits. This is inadequate for a mutation tool with zero annotation coverage.

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—two sentences that directly state the action and a key parameter requirement. Every word serves a purpose, with no redundancy or fluff, making it highly efficient and front-loaded.

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?

Given that there is an output schema (which handles return values) and only 2 parameters, the description is minimally complete. However, as a mutation tool with no annotations, it should ideally include more behavioral details (e.g., side effects, prerequisites) to be fully helpful, leaving room for improvement.

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 description adds meaningful context for the 'schedule_time' parameter by specifying the required ISO 8601 UTC format, which isn't covered in the schema (0% coverage). However, it doesn't explain 'campaign_id' (e.g., what constitutes a valid ID), leaving some semantic gaps. Since there are only 2 parameters and partial compensation, a score of 4 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 ('Schedule') and resource ('a campaign'), making the purpose evident. However, it doesn't distinguish this tool from potential siblings like 'send_campaign' or 'replicate_campaign', which might involve timing or scheduling aspects, so it doesn't reach the highest score.

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. For example, it doesn't clarify if this is for initial scheduling versus rescheduling, or how it relates to tools like 'send_campaign' or 'update_campaign'. This lack of context leaves usage ambiguous.

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

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