HeyLead

by D4umak

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

prospect

Destructive

Skip, close, or dismiss a lead in an outreach campaign. Record won, lost, or opt-out outcomes with reasons.

Instructions

Skip a prospect, close one with an outcome, or dismiss it.

Someone who is not a fit is skipped, not closed: skip leaves them out of
this campaign and records nothing else. Close records a result and
needs an outcome; won and lost are for people HeyLead has written to.
Closing with outcome="opt_out" stops all future contact with that person.
Reading a prospect is prospect_view.

Args:
    action: "skip", "close" or "dismiss".
    outreach_id: Which outreach.
    campaign_id: Which campaign. Uses the active one if empty.
    outcome: "won", "lost" or "opt_out". Required for close; there is
        no default.
    reason: Why, recorded with the outcome.
    meeting_link: The booked meeting, recorded with a won outcome.
    confirm: Required where the action cannot be undone.
    reason_code: Why, for skip and close: "not_a_fit", "negative_reply",
        "asked_to_stop", "handled_elsewhere" or "other".
    reason_note: A free note alongside the code.
    deal_value: What the won deal is worth (close with outcome="won").
    deal_currency: Three-letter code, e.g. USD. Defaults to the last deal's.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`action`	Yes
`reason`	No
`confirm`	No
`outcome`	No
`deal_value`	No
`campaign_id`	No
`outreach_id`	No
`reason_code`	No
`reason_note`	No
`meeting_link`	No
`deal_currency`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.10.429Oct 6, 2026
- changedInput schema / properties / outcome / default
```
Previous value: -"won"New value: +""
```

Changed2 schema fields changedv0.10.402Sep 26, 2026

addedInput schema / properties / deal_currency

Added value: +{
+  "default": "",
+  "title": "Deal Currency",
+  "type": "string"
+}

addedInput schema / properties / deal_value

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Deal Value"
+}

First observedv0.10.375Sep 18, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the description's job is to add detail, which it does: skip 'records nothing else,' close records a result, opt_out 'stops all future contact,' and confirm is 'required where the action cannot be undone.' It stops short of naming which specific actions are irreversible or what dismiss does relative to skip.

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?

Front-loaded with the three-action summary, then a prose block of selection rules, then a compact Args list. Every line is informative, though the reason/reason_code/reason_note trio is described somewhat repetitively.

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

Completeness4/5

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

With an output schema present, return values need not be explained, and the action semantics, conditional requirements and defaults are well covered. The remaining gap is 'dismiss,' which is listed but never distinguished from skip or close.

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 description coverage is 0% across 11 params, so the description must carry the load, and it does: it enumerates action, outcome and reason_code values inline, marks outcome as required for close with no default, and documents defaults for campaign_id ('active one if empty') and deal_currency ('last deal's'). This adds substantial meaning beyond the bare typed properties.

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 opening sentence states three specific actions (skip, close, dismiss) on a named resource, and the closing line explicitly routes the read case to prospect_view. An agent can distinguish this from the sibling prospect_view without opening either schema.

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?

It states the selection rule directly: 'Someone who is not a fit is skipped, not closed,' explains what close requires versus skip, and names the alternative tool for reading. Conditions for outcome="opt_out" are also given, so there is little left to infer.

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