Skip to main content
Glama
bcharleson

Instantly MCP Server

delete_lead

Destructive

Permanently remove a lead from all campaigns and lists while deleting all associated data and history. This action cannot be reversed.

Instructions

🗑️ PERMANENTLY delete a lead. CANNOT UNDO!

This action:

  • Removes the lead from all campaigns and lists

  • Deletes all lead data and history

  • Cannot be reversed

Confirm with user before executing!

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The core handler function that executes the delete_lead tool by calling the API DELETE /leads/{lead_id} endpoint.
    async def delete_lead(params: DeleteLeadInput) -> str:
        """
        🗑️ PERMANENTLY delete a lead. CANNOT UNDO!
        
        This action:
        - Removes the lead from all campaigns and lists
        - Deletes all lead data and history
        - Cannot be reversed
        
        Confirm with user before executing!
        """
        client = get_client()
        result = await client.delete(f"/leads/{params.lead_id}")
        return json.dumps({"success": True, "deleted": params.lead_id, **result}, indent=2)
  • Pydantic input schema for the delete_lead tool, requiring a lead_id.
    class DeleteLeadInput(BaseModel):
        """Input for deleting a lead. 🗑️ PERMANENTLY delete. CANNOT UNDO!"""
    
        model_config = ConfigDict(str_strip_whitespace=True, extra="ignore")
    
        lead_id: str = Field(..., description="Lead UUID to DELETE")
  • The LEAD_TOOLS list registers delete_lead among lead management tools, imported and dynamically registered in server.py.
    LEAD_TOOLS = [
        list_leads,
        get_lead,
        create_lead,
        update_lead,
        list_lead_lists,
        create_lead_list,
        update_lead_list,
        get_verification_stats_for_lead_list,
        add_leads_to_campaign_or_list_bulk,
        delete_lead,
        delete_lead_list,
        move_leads_to_campaign_or_list,
    ]
  • MCP annotations for the delete_lead tool, marking it as destructive and requiring confirmation.
    "delete_lead": {"destructiveHint": True, "confirmationRequiredHint": True},
    "delete_lead_list": {"destructiveHint": True, "confirmationRequiredHint": True},
Behavior5/5

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

The description adds significant behavioral context beyond the 'destructiveHint: true' annotation. It details specific effects: 'Removes the lead from all campaigns and lists' and 'Deletes all lead data and history,' and emphasizes 'CANNOT UNDO!' This provides actionable insights into the tool's destructive scope and permanence, enhancing the agent's understanding.

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 front-loaded with a clear warning ('🗑️ PERMANENTLY delete a lead. CANNOT UNDO!') followed by bullet points for key actions and a directive. Every sentence earns its place by reinforcing the tool's critical nature without redundancy, making it highly efficient and well-structured.

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 high complexity (destructive, permanent) and the presence of annotations and an output schema, the description is complete. It covers purpose, guidelines, behavioral details, and warnings, addressing all necessary context for safe invocation without needing to explain return values, which the output schema handles.

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 does not mention the 'lead_id' parameter explicitly. However, it implies the need for a lead identifier through context like 'delete a lead.' While it adds some meaning by clarifying the target, it doesn't detail parameter format or requirements, partially compensating for the schema gap.

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 explicitly states the action ('PERMANENTLY delete') and resource ('a lead'), distinguishing it from siblings like 'delete_campaign' or 'delete_lead_list' by specifying the target. It uses strong verbs and clear scope, making the purpose unmistakable.

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: 'Confirm with user before executing!' This indicates when to use (after user confirmation) and implies caution versus alternatives like 'update_lead' or 'deactivate' tools. It directly addresses the irreversible nature, guiding the agent on prerequisites.

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