Draftboard

View saved version →

---
name: draftboard-intros
description: Use when the user wants warm introductions, intro paths, or network-based outreach to a person or company — discovering who can introduce them to a prospect, checking if they're already connected to someone, finding their best intro opportunities, tracking intro progress, or writing outreach that name-drops mutual connections. Triggers include "warm intro", "who can introduce me to", "am I connected to", "best paths", "intro opportunities", "namedrop mutual connection", and any work against Draftboard targets/connections. Requires the hosted Draftboard MCP server at https://mcp.draftboard.com.
---

# Draftboard intros

Help the user get **warm introductions** using their Draftboard network data, through Draftboard's
hosted MCP server (`https://mcp.draftboard.com`). Draftboard's core idea is **relationship
proximity**: the shortest path from the user to a prospect (a **target**) runs through a mutual
**connection** (a **connector**), scored 0–100 by **rank**.

## Before anything else

1. Confirm the Draftboard tools are available. If they are missing, the connection has not been
   made — point the user to `references/setup.md`: it is one address and a browser approval, with
   nothing to install.
2. Call **`get_me`** once to confirm whose account this is (`customer.name` / `customer.user`). For
   "through my teammate" requests, the team roster is here too: match the teammate's name in
   `customer.teamMembers[]` and pass their `id` as `ownerIds`.
3. If a call comes back unauthorized, do **not** retry it and do not ask for a key — there is
   none. The connection was revoked or expired; tell the user to reconnect (`references/setup.md`),
   or to check **Settings → Connected apps** if they did not expect it to be gone.

## Pick the right tool

Prefer the **outcome tools** — they do the multi-step work and return a `telemetry` block so you
know how complete the answer is. Drop to **thin tools** only when no outcome tool fits.

| User wants… | Use |
|-------------|-----|
| Best intro opportunities right now | `find_top_paths` — one ranked call, one path per target |
| Paths through a specific teammate's network | `find_top_paths` with `ownerIds` |
| Several connectors for the SAME target (not just the strongest) | `get_target_connections` — `find_top_paths` returns only one (the strongest) path per target |
| **Paths only through people I'd actually ask** ("use my supporters", "only my 4–5 star people") | `find_top_paths` with **`ratings: [4,5]`** (2–5; one call — never cross-check a starred list against targets by hand). For one person: `get_target_connections` with `ratings` |
| Whether ONE named person is already a target (and their `targetId`) | `resolve_target` — one lookup, never a page walk |
| Whether they're already connected to people (by LinkedIn URL) | `check_if_connected` (a batch of URLs) |
| Progress of intros (new / completed / stopped) | `intro_status_overview` |
| Cold email that name-drops a mutual connection | `find_top_paths` (`includeRankDetails: true`), use `rankDetails` |
| Who can a specific connector introduce me to? | `get_connector_intros` (connector-first) |
| **Star / rate a connection** ("star this person", "mark them as a go-to", "rate them 5") | `set_connector_tier` with **`rating` 1–5, higher is better** (5 = ★★★★★ "ask anytime", 1 = ★ "don't ask" — which also hides them; `tier: 0` clears) |
| **My / a teammate's / the team's LinkedIn connections** ("my connections", "who does Alice know", export a network) | `get_me` → take the id (yours: `customerProfileId`; a teammate's: `teamMembers[].id`; if the name fits several people or none exactly, ask which one) → `list_network_connections` with `ownerIds`, paging until `nextPage` is 0; each row's `owners` says who on the team knows them |
| **List my starred / closest connections** ("who did I rate 5", "my go-tos") | `list_network_connections` with **`ratings: [5]`** (or `[4,5]`) |
| **Paths through a group** 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 4 — file references are metadata, not package contents.