Skip to main content
Glama
bcharleson

Instantly MCP Server

activate_campaign

Start sending email campaigns in Instantly.ai by activating a configured campaign with assigned accounts, leads, sequences, and schedule.

Instructions

Activate campaign to start sending.

Prerequisites (all required):

  1. At least one sender account assigned (email_list)

  2. At least one lead added to the campaign

  3. Email sequences configured

  4. Schedule configured

Use get_campaign to verify all prerequisites are met.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The primary handler function that executes the activate_campaign tool logic. It proxies the request to the Instantly API endpoint /campaigns/{campaign_id}/activate and returns the JSON response.
    async def activate_campaign(params: ActivateCampaignInput) -> str:
        """
        Activate campaign to start sending.
        
        Prerequisites (all required):
        1. At least one sender account assigned (email_list)
        2. At least one lead added to the campaign
        3. Email sequences configured
        4. Schedule configured
        
        Use get_campaign to verify all prerequisites are met.
        """
        client = get_client()
        result = await client.post(f"/campaigns/{params.campaign_id}/activate")
        return json.dumps(result, indent=2)
  • Pydantic input schema (BaseModel) for the activate_campaign tool, defining the required campaign_id parameter.
    class ActivateCampaignInput(BaseModel):
        """
        Input for activating a campaign.
        
        Prerequisites: accounts, leads, sequences, schedule must be configured.
        """
        
        model_config = ConfigDict(str_strip_whitespace=True, extra="ignore")
        
        campaign_id: str = Field(..., description="Campaign UUID to activate")
  • MCP tool registration annotation in the TOOL_ANNOTATIONS dictionary, specifying destructiveHint: False for the activate_campaign tool.
    "activate_campaign": {"destructiveHint": False},
  • List of campaign tools (CAMPAIGN_TOOLS) that includes activate_campaign, used by get_all_tools() for dynamic registration in the MCP server.
    CAMPAIGN_TOOLS = [
        create_campaign,
        list_campaigns,
        get_campaign,
        update_campaign,
        activate_campaign,
        pause_campaign,
        delete_campaign,
        search_campaigns_by_contact,
    ]
Behavior4/5

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

Annotations indicate 'destructiveHint: false', and the description adds valuable behavioral context not covered by annotations: it specifies prerequisites (sender accounts, leads, sequences, schedule) and references a verification tool. This enhances understanding of the tool's operational requirements beyond the non-destructive hint.

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 well-structured and concise, using bullet points for prerequisites and a clear follow-up sentence. Every sentence adds value without redundancy, making it easy to scan and understand quickly.

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

Completeness5/5

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

Given the tool's complexity (activating a campaign with prerequisites), the description is complete: it covers purpose, usage guidelines, and behavioral context. With annotations providing safety info and an output schema existing (though not shown), no additional details are needed for effective use.

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% description coverage, but the description compensates by implicitly clarifying the 'campaign_id' parameter through context (e.g., referencing prerequisites and 'get_campaign'). It doesn't fully detail parameter semantics like format examples, but adds meaningful context beyond the bare schema.

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 with the verb 'Activate' and resource 'campaign', specifying it's to 'start sending'. However, it doesn't explicitly differentiate from sibling tools like 'pause_campaign' or 'update_campaign' beyond the activation action, which keeps it from a perfect score.

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

Usage Guidelines5/5

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

The description provides explicit usage guidelines by listing four required prerequisites and recommending 'get_campaign' to verify them before use. This clearly indicates when to use this tool (after setup) and references an alternative tool for verification.

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/bcharleson/instantly-mcp-python'

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