HeyLead

Overview Schema Source Related Servers Discussions Admin

prospect

Destructive

Manage sales prospects during LinkedIn outreach: skip a campaign, close a deal, dismiss a lead, or review conversation history and timeline.

Instructions

Manage prospects — skip, close, dismiss, view conversation, or timeline.

Skip and Stop are different decisions:
  Skip — leave this person out of THIS campaign. No other effect.
  Stop — close(outcome='opt_out'): stop all outreach to this person
         across the workspace, and say why. That feedback improves
         targeting.

Args:
    action: What to do:
        "skip"         — Leave the prospect out of this campaign only
        "close"        — Record outcome (won/lost/opt_out) for an outreach
        "dismiss"      — Clear a lead off the Needs attention strip.
                         Closes it as lost, so it also leaves the Hot
                         Leads count. Needs confirm=True; the first call
                         previews who would be dismissed.
        "conversation" — View the full message thread with a prospect
        "timeline"     — View chronological journey of all actions for a prospect
    outreach_id: The outreach ID. Auto-selects if empty (except 'conversation'/'timeline').
    campaign_id: Which campaign (for 'skip'). Uses active if empty.
    outcome: 'won', 'lost', or 'opt_out' (for 'close').
    reason: Optional notes for the outcome (for 'close').
    meeting_link: Meeting/calendar URL if outcome is 'won' (for 'close').
        This is the URL where the meeting was booked — could be
        the user's booking page or the prospect's shared calendar.
    confirm: Must be True to actually dismiss (for 'dismiss').
    reason_code: Why, for 'skip' and 'close'. One of 'not_a_fit',
        'negative_reply', 'asked_to_stop', 'handled_elsewhere', 'other'.
        Only the first two are evidence about targeting; the rest are
        facts about that one person and never move a segment's ranking.
    reason_note: Free text alongside the code.

Input Schema

TableJSON Schema

Name	Required	Default
`action`	Yes
`reason`	No
`confirm`	No
`outcome`	No	won
`campaign_id`	No
`outreach_id`	No
`reason_code`	No
`reason_note`	No
`meeting_link`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.10.375Sep 18, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already indicate destructiveHint=true and openWorldHint=true, but the description adds substantial behavioral context: dismiss closes as lost and reduces Hot Leads count, confirm is mandatory, and the difference between evidence-based reason codes ('not_a_fit', 'negative_reply') versus fact-based ones is clearly explained. It also notes that skip has no side effects beyond the current campaign, and that stop affects all outreach. These details go well beyond the annotations and give the agent a clear picture of side effects and side constraints.

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 efficiently structured: a one-line summary, a two-line conceptual distinction that resolves a common ambiguity, then a bulleted list of arguments with terse explanations. Every sentence earns its place – the skip/stop clarification prevents misinterpretation, and the parameter list is dense but scannable. The use of code formatting and indentation improves readability without padding. For a tool with nine parameters, the length is proportionate and well organized.

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 complexity (9 parameters, multiple distinct actions, side effects on campaigns and leads), the description covers all necessary context: action semantics, parameter requirements, defaults, and consequences. The presence of an output schema means return-value details are not needed here. The description also addresses edge cases like auto-selection of outreach_id and the preview behavior of dismiss. An agent would have sufficient information to invoke the tool correctly for any of the five actions without consulting additional documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% – the schema provides no property descriptions – so the description fully compensates. Every parameter is explained: action lists all six values with specific behaviors, outreach_id auto-selects if empty except for conversation/timeline, campaign_id defaults to active for skip, outcome defaults to 'won' but explained, meeting_link is clarified for 'won', confirm must be True for dismiss, and reason_code enumerates valid values with targeting implications. reason_note is described as free text. No parameter is left opaque.

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 opens with a clear verb-resource pairing ('Manage prospects') and enumerates five specific actions: skip, close, dismiss, view conversation, or timeline. It distinguishes skip from stop/close with a precise semantic difference, making the tool's purpose unmistakable and differentiating it from vague alternatives. The description goes beyond a generic summary by specifying exact behaviors for each action.

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

Usage Guidelines4/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 each action, especially the critical distinction between 'skip' and 'stop' (close with opt_out), including the workspace-wide effect of stop and the targeting feedback implication. It also specifies that 'dismiss' requires confirm=True and previews on first call. However, it does not explicitly name alternative sibling tools or state when those should be used instead, though the action-level guidance is thorough enough for most usage decisions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.