Skip to main content
Glama
bcharleson

Instantly MCP Server

delete_lead_list

Destructive

Permanently delete a lead list from Instantly.ai after user confirmation. This action removes the list and may orphan leads, and cannot be reversed.

Instructions

🚨 PERMANENTLY delete a lead list. CANNOT UNDO!

⚠️ REQUIRES USER CONFIRMATION before executing!

This action:

  • Permanently removes the lead list

  • Leads in the list may be orphaned (check your workflow)

  • Cannot be reversed

Before calling this tool, you MUST:

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

  2. Verify the list_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 main handler function for the delete_lead_list tool. It performs a permanent deletion of the specified lead list via the API client and returns a success message.
    async def delete_lead_list(params: DeleteLeadListInput) -> str:
        """
        🚨 PERMANENTLY delete a lead list. CANNOT UNDO!
    
        ⚠️ REQUIRES USER CONFIRMATION before executing!
    
        This action:
        - Permanently removes the lead list
        - Leads in the list may be orphaned (check your workflow)
        - Cannot be reversed
    
        Before calling this tool, you MUST:
        1. Confirm with the user that they want to delete this list
        2. Verify the list_id is correct
        3. Warn them this action cannot be undone
        """
        client = get_client()
        result = await client.delete(f"/lead-lists/{params.list_id}")
        return json.dumps({
            "success": True,
            "deleted_list_id": params.list_id,
            "message": "Lead list permanently deleted",
            **result
        }, indent=2)
  • Pydantic input model for the delete_lead_list tool, defining the required list_id parameter.
    class DeleteLeadListInput(BaseModel):
        """
        Input for deleting a lead list. ⚠️ PERMANENT - CANNOT UNDO!
    
        Requires user confirmation before executing.
        """
    
        model_config = ConfigDict(str_strip_whitespace=True, extra="ignore")
    
        list_id: str = Field(..., description="Lead List UUID to DELETE PERMANENTLY")
  • MCP tool annotation registration in server.py, marking delete_lead_list as destructive and requiring confirmation.
    "delete_lead_list": {"destructiveHint": True, "confirmationRequiredHint": True},
  • Local registration of delete_lead_list in the LEAD_TOOLS list, used by the server to collect and register tools.
    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,
    ]
Behavior4/5

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

The annotations provide destructiveHint=true, which the description reinforces with 'PERMANENTLY delete' and 'CANNOT UNDO!'. It adds valuable context beyond annotations: the requirement for user confirmation, the potential for orphaned leads, and the irreversible nature. No contradiction with annotations exists.

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 information ('🚨 PERMANENTLY delete...'). Every sentence adds value, such as consequences and prerequisites, with no redundant or wasted text. The use of emojis and formatting enhances clarity without sacrificing efficiency.

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 operation) and the presence of an output schema (which handles return values), the description is complete. It covers purpose, usage guidelines, behavioral risks, and parameter importance, addressing all necessary aspects for safe and 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?

With 0% schema description coverage (the schema only has a generic warning), the description compensates by emphasizing the criticality of the list_id parameter ('Verify the list_id is correct') and its role in identifying the lead list to delete. It adds meaningful context about parameter handling, though it doesn't detail the UUID format.

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 lead list'), distinguishing it from sibling tools like delete_account, delete_campaign, and delete_lead by specifying the target resource type. It uses strong, unambiguous language that leaves no doubt about the tool's function.

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 mandates user confirmation, verification of the list_id, and a warning about irreversibility before execution. It implicitly distinguishes from other deletion tools by focusing on lead lists, though it doesn't name specific alternatives.

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