Skip to main content
Glama

schedule_campaign

Schedule email campaigns for future delivery by setting a specific date and time, enabling planned newsletter distribution.

Instructions

Schedule a campaign for future delivery.

Args: campaign_id: The campaign ID (e.g. "mc_12345"). scheduled_for: ISO 8601 datetime (e.g. "2026-03-15T14:00:00Z").

Returns: The updated campaign record with scheduled_for set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYes
scheduled_forYes

Implementation Reference

  • The actual API implementation for scheduling a campaign.
    def schedule_campaign(self, campaign_id: str, scheduled_for: str) -> dict:
        """Schedule a campaign for future delivery."""
        resp = self.session.post(f"{self.url}/api/v1/campaigns/{campaign_id}/actions/schedule",
                                json={"data": {"scheduled_for": scheduled_for}},
                                headers=self._headers(), timeout=30)
        resp.raise_for_status()
        return resp.json()
  • mcp_server.py:203-215 (registration)
    The MCP tool registration and wrapper that calls the client implementation.
    @mcp.tool()
    def schedule_campaign(campaign_id: str, scheduled_for: str) -> dict:
        """
        Schedule a campaign for future delivery.
    
        Args:
            campaign_id: The campaign ID (e.g. "mc_12345").
            scheduled_for: ISO 8601 datetime (e.g. "2026-03-15T14:00:00Z").
    
        Returns:
            The updated campaign record with scheduled_for set.
        """
        return _client.schedule_campaign(campaign_id, scheduled_for=scheduled_for)
Behavior3/5

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

With no annotations provided, the description carries the full burden but only partially succeeds. It discloses the return value ('updated campaign record with scheduled_for set') and datetime format requirements, but omits critical behavioral details like state transitions, idempotency, or valid campaign statuses for scheduling.

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?

Excellent structure with clear Args and Returns sections. Every sentence earns its place: opening declaration, parameter documentation, and return value explanation with no redundant text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Good completeness for a 2-parameter tool without annotations or output schema: it explains the mutation behavior and return value. Minor gap: lacks mention of valid campaign states or error conditions (e.g., attempting to schedule already-sent campaigns).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema description coverage, the description fully compensates by documenting both parameters with clear semantic meaning and format examples (e.g., 'mc_12345' for ID, ISO 8601 datetime with example).

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

Purpose5/5

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

The description clearly states the specific action (Schedule) and resource (campaign) with scope (future delivery), effectively distinguishing it from sibling 'send_campaign' (immediate) and 'create_campaign' (creation).

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

While 'future delivery' implicitly contrasts with immediate sending, the description lacks explicit guidance on when to use this versus 'send_campaign' or prerequisites (e.g., campaign must exist and be in a valid state).

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/gwbischof/keila-mcp'

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