Skip to main content
Glama
bcharleson

Instantly MCP Server

delete_campaign

Destructive

Permanently remove an email outreach campaign and all associated data from Instantly.ai. Requires user confirmation as this action cannot be undone.

Instructions

🚨 PERMANENTLY delete a campaign. CANNOT UNDO!

⚠️ REQUIRES USER CONFIRMATION before executing!

This action:

  • Permanently removes the campaign

  • Deletes all campaign data, sequences, and settings

  • Removes leads from this campaign (leads themselves are NOT deleted)

  • Cannot be reversed

Before calling this tool, you MUST:

  1. Confirm with the user that they want to delete this campaign

  2. Verify the campaign_id is correct

  3. Warn them this action cannot be undone

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The async handler function that executes the delete_campaign tool by calling the API DELETE /campaigns/{campaign_id} and returns a formatted success JSON.
    async def delete_campaign(params: DeleteCampaignInput) -> str:
        """
        🚨 PERMANENTLY delete a campaign. CANNOT UNDO!
    
        ⚠️ REQUIRES USER CONFIRMATION before executing!
    
        This action:
        - Permanently removes the campaign
        - Deletes all campaign data, sequences, and settings
        - Removes leads from this campaign (leads themselves are NOT deleted)
        - Cannot be reversed
    
        Before calling this tool, you MUST:
        1. Confirm with the user that they want to delete this campaign
        2. Verify the campaign_id is correct
        3. Warn them this action cannot be undone
        """
        client = get_client()
        result = await client.delete(f"/campaigns/{params.campaign_id}")
        return json.dumps({
            "success": True,
            "deleted_campaign_id": params.campaign_id,
            "message": "Campaign permanently deleted",
            **result
        }, indent=2)
  • Pydantic input schema model for the delete_campaign tool, defining the required campaign_id field.
    class DeleteCampaignInput(BaseModel):
        """
        Input for deleting a campaign. ⚠️ PERMANENT - CANNOT UNDO!
    
        Requires user confirmation before executing.
        """
    
        model_config = ConfigDict(str_strip_whitespace=True, extra="ignore")
    
        campaign_id: str = Field(..., description="Campaign UUID to DELETE PERMANENTLY")
  • The CAMPAIGN_TOOLS list exports the delete_campaign function for 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,
    ]
  • MCP tool annotations in TOOL_ANNOTATIONS dict marking delete_campaign as destructive and requiring confirmation.
    "delete_campaign": {"destructiveHint": True, "confirmationRequiredHint": True},
Behavior4/5

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

The annotations provide destructiveHint=true, but the description adds substantial behavioral context beyond this: it details what gets destroyed (campaign data, sequences, settings), clarifies what happens to leads (removed from campaign but not deleted), and emphasizes the irreversible nature. It doesn't contradict the destructiveHint annotation, but provides richer behavioral information.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded with the most critical warning. Every sentence earns its place by providing essential warnings, behavioral details, or usage requirements. The structure moves from dire warning to specific consequences to mandatory prerequisites in a logical flow.

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 this is a highly destructive tool with only one annotation (destructiveHint), the description provides excellent completeness. It covers the irreversible nature, specific data affected, prerequisites for use, and warnings. With an output schema present, it doesn't need to explain return values, and it fully addresses the tool's critical behavioral aspects.

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?

With 0% schema description coverage, the description compensates well by providing semantic context for the single parameter. While it doesn't explicitly name 'campaign_id', it repeatedly references verifying 'campaign_id' in the usage guidelines and mentions 'Campaign UUID' in the schema. The description adds meaning about the parameter's critical importance for this destructive operation.

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 ('PERMANENTLY delete') and resource ('a campaign'), distinguishing it from sibling tools like 'delete_account', 'delete_lead', or 'delete_lead_list' which target different resources. The use of 'PERMANENTLY' and 'CANNOT UNDO!' emphasizes the irreversible nature of this deletion operation.

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 guidance on when to use this tool: it lists three prerequisites that MUST be met before calling (user confirmation, campaign_id verification, warning about irreversibility). It also implicitly distinguishes from alternatives like 'pause_campaign' or 'update_campaign' by emphasizing the permanent deletion aspect.

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