Skip to main content
Glama
bcharleson

Instantly MCP Server

update_lead_list

Modify lead list details including name, enrichment settings, or ownership within the Instantly.ai email outreach platform.

Instructions

Update lead list name, enrichment settings, or owner.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The core handler function that executes the update_lead_list tool by sending a PATCH request to the Instantly API to update lead list name, enrichment settings, or owner.
    async def update_lead_list(params: UpdateLeadListInput) -> str:
        """
        Update lead list name, enrichment settings, or owner.
        """
        client = get_client()
        
        body: dict[str, Any] = {}
        
        if params.name is not None:
            body["name"] = params.name
        if params.has_enrichment_task is not None:
            body["has_enrichment_task"] = params.has_enrichment_task
        if params.owned_by is not None:
            body["owned_by"] = params.owned_by
        
        result = await client.patch(f"/lead-lists/{params.list_id}", json=body)
        return json.dumps(result, indent=2)
  • Pydantic schema defining the input parameters for the update_lead_list tool: list_id (required), optional name, has_enrichment_task, owned_by.
    class UpdateLeadListInput(BaseModel):
        """Input for updating a lead list."""
        
        model_config = ConfigDict(str_strip_whitespace=True, extra="ignore")
        
        list_id: str = Field(..., description="List UUID")
        name: Optional[str] = Field(default=None)
        has_enrichment_task: Optional[bool] = Field(default=None)
        owned_by: Optional[str] = Field(default=None)
  • MCP tool registration annotation specifying that update_lead_list is non-destructive.
    "update_lead_list": {"destructiveHint": False},
  • Tool function included in LEAD_TOOLS list for collection by get_all_tools() in server.py.
    update_lead_list,
  • LEAD_TOOLS list that exports all lead-related tools, including update_lead_list, for dynamic loading in the server.
    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,
    ]
Behavior3/5

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

The annotations provide 'destructiveHint: false', indicating this is a non-destructive operation. The description adds value by specifying updatable fields (name, enrichment settings, owner), which clarifies the scope of changes. However, it lacks behavioral details like permission requirements, whether updates are partial or overwrite all fields, or rate limits. 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.

Conciseness5/5

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

The description is a single, efficient sentence with zero waste. It front-loads the core action ('Update lead list') and specifies key updatable aspects. Every word adds value, making it easy for an agent to parse quickly.

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

Completeness3/5

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

Given the tool has annotations (destructiveHint) and an output schema (implied by context signals), the description doesn't need to cover safety or return values. However, as a mutation tool with 0% schema coverage and no usage guidelines, it leaves gaps in parameter understanding and context. It's minimally adequate but lacks depth for effective agent use.

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?

Schema description coverage is 0%, so the schema provides no parameter descriptions. The description compensates by listing updatable fields (name, enrichment settings, owner), which map to parameters in the schema. However, it doesn't explain 'list_id' (the required parameter) or provide details on format, constraints, or default behaviors for nullable fields. Baseline is 3 due to partial compensation.

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 action ('Update') and target resource ('lead list'), and specifies what can be updated ('name, enrichment settings, or owner'). It distinguishes from siblings like 'create_lead_list' and 'delete_lead_list' by focusing on modification rather than creation or deletion. However, it doesn't explicitly differentiate from other update tools like 'update_account' or 'update_campaign' beyond the resource name.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing list), exclusions (e.g., what cannot be updated), or comparisons to siblings like 'create_lead_list' for new lists or 'get_lead' for read-only access. The agent must infer usage from the tool name alone.

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