Skip to main content
Glama
bcharleson

Instantly MCP Server

pause_campaign

Pause an active email campaign to immediately stop all sending while retaining leads and pausing sequences. Use to temporarily halt outreach without removing campaign data.

Instructions

Pause campaign to stop sending.

Effects:

  • Immediately stops all email sending

  • Leads remain in the campaign

  • In-progress sequences are paused

Use activate_campaign to resume sending.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'pause_campaign' tool. It takes PauseCampaignInput, calls the Instantly API to pause the campaign via POST /campaigns/{campaign_id}/pause, and returns the JSON result.
    async def pause_campaign(params: PauseCampaignInput) -> str:
        """
        Pause campaign to stop sending.
    
        Effects:
        - Immediately stops all email sending
        - Leads remain in the campaign
        - In-progress sequences are paused
    
        Use activate_campaign to resume sending.
        """
        client = get_client()
        result = await client.post(f"/campaigns/{params.campaign_id}/pause")
        return json.dumps(result, indent=2)
  • Pydantic input schema for the pause_campaign tool, requiring a single 'campaign_id' field.
    class PauseCampaignInput(BaseModel):
        """
        Input for pausing a campaign.
    
        Stops sending but leads remain. Use activate_campaign to resume.
        """
    
        model_config = ConfigDict(str_strip_whitespace=True, extra="ignore")
    
        campaign_id: str = Field(..., description="Active campaign UUID")
  • MCP tool registration annotation specifying that pause_campaign is non-destructive.
    "pause_campaign": {"destructiveHint": False},
  • Registration of pause_campaign in the CAMPAIGN_TOOLS list, which is collected by get_all_tools() for server registration.
    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?

The description adds valuable behavioral context beyond the annotations. While annotations only indicate destructiveHint=false, the description details specific effects: 'Immediately stops all email sending', 'Leads remain in the campaign', and 'In-progress sequences are paused'. This provides crucial operational information not captured in annotations.

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 perfectly structured and concise. It starts with the core purpose, lists specific effects in bullet points for clarity, and ends with usage guidance. Every sentence earns its place with zero wasted words.

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 moderate complexity, the presence of annotations, and an output schema, the description is complete. It covers purpose, effects, and usage guidance. The output schema existence means the description doesn't need to explain return values, making this description fully adequate.

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?

With 0% schema description coverage, the description doesn't provide any parameter information beyond what's implied by the tool name. The schema already documents the single 'campaign_id' parameter with its description, so the description adds no additional parameter semantics. This meets the baseline for high schema coverage situations.

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 ('Pause campaign to stop sending') and distinguishes it from siblings by mentioning 'activate_campaign to resume sending'. It specifies the exact effect on email sending, which differentiates it from deletion or other campaign management tools.

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 explicitly states when to use this tool ('Pause campaign to stop sending') and when to use an alternative ('Use activate_campaign to resume sending'). It provides clear context about the tool's purpose versus its sibling activate_campaign.

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