cancel_network_sync_tool
ChatGPTCancel or remove one pending network sync by its queue row id. Use when the user asks to cancel or remove a pending sync. Pass queue_entry_id from sync.id on the queue_network_sync_tool or queue_network_sync_status_tool result for that job. If you do not have an id, call queue_network_sync_status_tool with the same social_path, teamDomainScope, and collaborator_pkid as the original queue_network_sync_tool call first. If sync is null, there is nothing to cancel. Call once per id. For several jobs, call once each. On outcome deleted, tell the user the pending sync was removed. On outcome reverted, tell the user it was removed from the queue and the last completed result is still there. On HTTP 400, tell the user it is no longer waiting and was not canceled. Do not retry a processing row. On HTTP 409, retry that same id once. If the retry returns outcome reverted, say it was taken off the queue and the previous result was kept. If the retry is HTTP 400, say it is no longer waiting and was not canceled. On HTTP 401, tell the user they can only cancel a sync they requested or queued. On timeout, the cancel may have completed; call queue_network_sync_status_tool with the same scope before retrying cancel.
enrich_company_by_linkedin_tool
ChatGPTTrigger enrichment for a company by LinkedIn (enrich company by LinkedIn). Use when the user asks to enrich a company by LinkedIn, trigger company enrichment by LinkedIn, or send a company LinkedIn URL for enrichment. Distinct from a future enrich-company-by-domain tool. Input: Provide a LinkedIn company URL (full or partial) or company slug. - Full URL: https://www.linkedin.com/company/gambit-robotics-inc/ - Partial or slug: anthropic or linkedin.com/company/anthropic Optional teamDomainScope: team FQDN (e.g. acme.com) to evaluate plan gates against that team's plan (same domain as search_network.teamDomainScope / enrich_person.teamDomainScope). Omit for personal scope. Returns success with the normalized URL that was submitted, or an error. Enrichment runs asynchronously; after processing, use search_network to find people by the company's domain (e.g. credentialnames:Verified: companydomain.com).
enrich_person_tool
ChatGPTTrigger enrichment for a person by LinkedIn URL. Use when the user asks to "enrich person [name]", "enrich [LinkedIn URL]", "enrich [name]", "get contact info for [person]", or similar. Input: Provide a LinkedIn URL (full or partial) or a LinkedIn username. - Full URL: https://www.linkedin.com/in/kbieg/ - Partial or username: kbieg or linkedin.com/in/kbieg - If the user gives only a person's name (e.g. "Kyle Bieg"), use search_network or another method to find their LinkedIn profile URL first, then call this tool with that URL. Optional teamDomainScope: team FQDN (e.g. acme.com) when enriching on behalf of a team. Omit it: scope defaults to personal. Prefer company_domain from get_entitlements when it is a hostname, or a team the user named, and pass the same teamDomainScope on every enrich_person and get_enrichment_result call. Ask only if scope is unclear. Teammates can then retrieve the result without a further charge. Returns success with the normalized LinkedIn URL submitted, or an error. Enrichment is asynchronous. After a short delay (e.g. 30–60 seconds), call get_enrichment_result with the same LinkedIn URL (and same teamDomainScope if used) to retrieve contact info.
get_enrichment_result_tool
ChatGPTCheck enrichment status or retrieve result for a person by social path or LinkedIn URL. Use after calling enrich_person: enrichment is asynchronous; call this after a short delay of 30 to 60 seconds to get contact info. Input: Either a social path (e.g. linkedin/johndoe, twitter/handle) or a LinkedIn URL/username (same format as enrich_person). Optional teamDomainScope: team FQDN (e.g. acme.com) when retrieving a team-scoped enrichment. Omit it: scope defaults to personal. Prefer company_domain from get_entitlements when it is a hostname, or a team the user named, and pass the same teamDomainScope used in enrich_person. Ask only if scope is unclear. Teammates on that team retrieve the record without a further charge. Checking status or retrieving a record the user or their team submitted is covered by their plan or per-call billing. Retrieving someone else's contact data may require a higher plan; if it is not covered, the tool explains what is available instead. Returns: status, emails, phones, fullName, jobTitle, location. Phone numbers and extended emails are not part of every plan, so treat them as optional rather than missing data.
get_entitlements_tool
ChatGPTReturn the user's Icebreaker plan, subscription status and per-feature limits. teamDomainScope: Optional company domain (e.g. "acme.com") to inspect that team's limits instead of the user's own. Omit for personal scope. If the returned company_domain is a hostname, pass it as teamDomainScope on later tools unless the user named a different team or asked for personal scope.
get_intro_path_tool
ChatGPTFind intro path(s) from you (the viewer) to a single contact using 1st-degree connections. IMPORTANT: Use for ONE contact at a time only. If the user asks about multiple people, call this tool separately for each contact. Do not pass social paths from multiple different profiles in a single call. Use this when the user is looking at search results and wants to find someone who can introduce them to a specific profile. Pass that single target profile's social path(s) in connected_social_paths. Viewer context is always available here from the user's signed-in Icebreaker session. HARDWIRED PAYLOAD: - ordinality: ["1st"] (direct connections only) - connectedSocialPaths: [list of social paths from the connected_social_paths argument] (required) - sortBy: "signal_score" (results always sorted by signal score) - hideViewer: true, sources: ["all"], limit: configurable (default 50)
get_list_tool
ChatGPTRead one contact list by ID with a paginated slice of member social paths (up to 1000 per page from the API). The lists API returns page, total_pages, and total_members on each response when supported; the MCP forwards that page of social_paths without re-slicing. Older responses that omit pagination metadata are paginated client-side for compatibility. Paths use supported prefixes only (linkedin/, github/, twitter/, farcaster/, profile/). Profile enrichment is up to the caller. Viewer context is always available here from the user's signed-in Icebreaker session. List GET requests always send your pkid as owner and viewer. Pass teamDomainScope to scope to a team; when omitted, queries personal lists (no inference from viewer context).
get_mutuals_tool
ChatGPTReturn mutual 1st-degree connections between you (the viewer) and one or more target profiles. Use this for "what do we have in common?" or "who can vouch for me?" — same graph data as intro path, but framed as shared connections. Pass the target profile's social path(s) in connected_social_paths. Viewer context is always available here from the user's signed-in Icebreaker session. HARDWIRED PAYLOAD: - ordinality: ["1st"] (direct connections only) - connectedSocialPaths: [list of social paths from the connected_social_paths argument] (required) - sortBy: "signal_score" - hideViewer: true, sources: ["all"], limit: configurable (default 50)
get_server_instructions
ChatGPTIcebreaker search-first guide: prefer search_network, when to call lookup_viewer to check linked_accounts before prompting to link, when to call get_started, standing search defaults, and how to present results. Same text as the server_instructions prompt, resource://search-guide, and the MCP instructions field. Use this tool when prompts and resources are unavailable in the client. For connecting a new user's network after lookup_viewer shows none linked (or after an empty search), call get_started instead.
get_started
ChatGPTQuickest path to a first useful Icebreaker search: connect accounts, optionally join a team, then run a first search. Call this when the user asks how to get started, how to use Icebreaker, how to set up Icebreaker, what to do first, or how to connect their LinkedIn, GitHub or X network. Also call it after lookup_viewer shows no linked accounts, or after an Icebreaker search succeeds but returns no results. Do not call this before trying search_network when accounts may already be linked. Prefer lookup_viewer first to check linked_accounts. Static guidance only. Do not include MCP install or connection-setup steps.
get_team_collaborators
ChatGPTReturn team collaborators with profile info and social paths on your team (same endpoint as get_team with teamCollaborators=collaborators). get_team uses teamCollaborators=verified (verified members only); this tool lists collaborators only. Team is defined by verified company credential members. Only paths with supported prefixes are returned: icebreaker/, profile/, linkedin/, farcaster/, github/, twitter/. Pass the returned social_paths as connectedSocialPaths to search_network for a collaborator-scoped search. When queueing a collaborator network sync, pass only a non-empty pkid from this response. If pkid is missing, do not call queue_network_sync for that person — omitting it syncs the signed-in user's own network. omni_profile.name helps pick the right person. Viewer context is always available here from the user's signed-in Icebreaker session.
get_team_tool
ChatGPTReturn the list of social paths for your team (Verified + collaborators). Team is defined by verified company credential members. Only paths with supported prefixes are returned: icebreaker/, profile/, linkedin/, farcaster/, github/, twitter/. Use get_team first to obtain social_paths, then pass that list as connectedSocialPaths to search_network (up to 1000 paths per request) to run a team-scoped search. Viewer context is always available here from the user's signed-in Icebreaker session.
invite_team_collaborator
ChatGPTSend a collaborator invite email for your team. Use when you are a team admin or collaborator and want someone (for example a founder) to join the team as a collaborator. They receive the same email invite as from the Teams page. email is the invitee address. teamDomainScope is required (the team domain, e.g. backpocket.vc). Out of scope: promoting an existing user, making admin, or removing members.
list_lists_tool
ChatGPTList all contact lists for the viewer (GET /lists). Uses your pkid for owner and viewer, with optional domain for team-scoped lists. Does not return member paths — use get_list for members. Viewer context is always available here from the user's signed-in Icebreaker session.
list_network_syncs_tool
ChatGPTList network sync queue entries for the signed-in viewer (read-only). Use when the user asks what syncs are queued, running, or completed. Returns paginated sync rows plus aggregate counts (counts ignore any status filter). For one social path's status, use queue_network_sync_status_tool instead. Optional teamDomainScope and collaborator_pkid list a team collaborator's syncs; same semantics as queue_network_sync_status_tool (team admin on that domain, collaborator on the team). HTTP GET to the configured network sync queue webhook URL with /list appended.
lookup_viewer_tool
ChatGPTLookup the viewer's profile and all connected profiles (LinkedIn, etc.). This tool fetches comprehensive profile data for the current viewer using the search query: - socialPaths: ["icebreaker/viewer_pkid"] - sources: ["all"] - ordinality: ["Global"] - limit: 100 Returns all profiles associated with the viewer across platforms including: - Primary profile information - All connected social profiles (LinkedIn, GitHub, etc.) - Work history and experience across platforms - Contact information and social links Viewer context is always available here from the user's signed-in Icebreaker session.
make_team_collaborator
ChatGPTMake someone a team collaborator immediately from an external profile. Use on a paid team when you know their email and the person is a non-platform profile who is either a verified member of that team or in your 1st-degree network. The server creates their account from the profile's LinkedIn, GitHub, or X, sets the collaborator role, and sends the made-collaborator email. The profile must be domain-verified for this team or a 1st-degree connection of the viewer. Flagged members and existing platform users are rejected. If that email is already an admin or collaborator, the call succeeds and reports they are already on the team. On a paid team, use invite_team_collaborator when the person is neither domain-verified nor in your 1st-degree network (pending invite email). Both MCP tools require a starter-or-higher team plan. email is required. profileID is the Icebreaker profile route id (e.g. linkedin-jane-doe). teamDomainScope is required.
manage_list_tool
ChatGPTCreate a list or add/remove members or update name/description/share_state. Actions: create (name + social_paths required; optional teamDomainScope for team lists), add_members, remove_members (list_id + social_paths), update (list_id + name and/or description and/or share_state). On create, owner and creator are always your pkid; teamDomainScope is optional. System lists (creator: icebreaker) cannot be modified. Viewer context is always available here from the user's signed-in Icebreaker session. Every POST to the lists API includes viewer (your pkid) in the JSON body. Create also sends owner and creator as your pkid, with optional domain for team lists. After a successful create (or any action returning an id), construct and surface the list URL: - Personal lists: https://app.icebreaker.xyz/lists/{id} - Team lists (when teamDomainScope was provided): https://app.icebreaker.xyz/teams/{teamDomainScope}/lists/{id}
queue_network_sync_status_tool
ChatGPTRead network-sync queue status for a social path (read-only; does not queue, start, or cancel syncs). Companion to queue_network_sync_tool: use the same social_path (channel/identifier, e.g. linkedin/johndoe for linkedin, twitter, or github only). This tool issues HTTP GET to the configured network sync queue webhook URL with that path appended (URL-encoded). Query string: requestedByPKID (signed-in viewer), and when set collaboratorPKID and teamDomain. Optional Authorization Bearer uses the configured webhook secret. Request timeout is 30 seconds.
queue_network_sync_tool
ChatGPTQueue a social path for syncing the viewer's social graph. Use when the user wants to sync their LinkedIn, Twitter, or GitHub network. Accepts a social path in the form channel/identifier (e.g. linkedin/johndoe, twitter/handle, github/octocat). teamDomainScope is optional: omit for personal scope; pass a team FQDN to scope the sync to that team. If the user identifies someone by name or partial information instead of a social path (e.g. "sync John Smith" or "add the CTO of Acme Corp"), resolve their handles first: 1. Call search_network with the person's name and any known context (company, role, location) to find matching profiles. 2. Extract the social path from the result. Prefer linkedin/... paths, then twitter/..., then github/.... Only these three channel prefixes are accepted; no other path format works. 3. Call queue_network_sync with that social_path. If search_network returns no clear match, ask the user to confirm the desired social path before queuing. Optional collaborator_pkid queues a sync on behalf of a team collaborator. Pass only a non-empty pkid from a get_team_collaborators result. If pkid is missing, do not queue a collaborator sync — omitting collaborator_pkid syncs the signed-in user's own network. When collaborator_pkid is set: - teamDomainScope is required: pass the team FQDN explicitly. Omitting it means personal scope; a team is never inferred. - Only a team admin can queue a sync for a collaborator, and the collaborator must be on that same team. Both are checked before the sync is queued. - social_path is the network to sync and need not belong to the collaborator. Call get_team_collaborators(company_domain=teamDomainScope) to list the team.
search_network
ChatGPTSearch the user's Icebreaker network for people: candidates, prospects, and paths to a warm intro. The signed-in user's viewer context is always available here. Default ordinality: ["1st", "2nd"] (["1st"] for direct connections only). Use ["Global"] only for a handle lookup with socialPaths, another person's network with connectedSocialPaths, or a team search with connectedSocialPaths from get_team. Never ask the user for a viewer id and never set viewerPkid yourself. RESULT FORMAT (required): present every person with a link. Use the profile's profile_url; if it is missing, build the link from omni_profile.social_name (profile/xyz becomes https://app.icebreaker.xyz/profiles/xyz, linkedin/abc123 becomes https://app.icebreaker.xyz/linkedin/abc123). Take name and bio from omni_profile. PAGINATION: results are capped at 100 per call. Increment offset by the requested limit (for example 0, then 50 when limit is 50) and stop when a page returns fewer profiles than limit. For a full scan, such as every member of a company, paginate until exhausted. QUICK START: - "find golang engineers in nyc": {"globs": ["golang engineer New York"], "ordinality": ["1st", "2nd"], "limit": 50, "hideViewer": true, "sources": ["all"]} - "find rust developers": {"globs": ["rust developer"], "ordinality": ["1st", "2nd"], "limit": 50, "hideViewer": true, "sources": ["all"]} - "find people at coinbase": {"globs": ["credentialnames:Verified: coinbase.com"], "ordinality": ["1st", "2nd"], "limit": 50, "hideViewer": true, "sources": ["all"]} - "look up linkedin user hoangmn": {"socialPaths": ["linkedin/hoangmn"], "ordinality": ["Global"], "limit": 50, "hideViewer": true, "sources": ["all"]} - "engineers in hoangmn's network": {"connectedSocialPaths": ["linkedin/hoangmn"], "globs": ["engineer"], "ordinality": ["Global"], "limit": 50, "hideViewer": true, "sources": ["all"]} PARAMETERS: - globs: skills, roles and location in one string, e.g. ["golang engineer New York"] or ["rust web3 San Francisco"]. Combine several skills in one string rather than separate entries. - ordinality: ["1st", "2nd"] (["1st"] for direct connections only). Use ["Global"] only for a handle lookup with socialPaths, another person's network with connectedSocialPaths, or a team search with connectedSocialPaths from get_team. - hideViewer: always true, so the user is not returned to themselves. - sources: ["all"] to search every platform. - limit: 50 to 100 for a first search. - locations: deprecated, put the location in globs instead. - socialPaths: look up specific profiles by handle and get those exact profiles back, not their connections. Allowed prefixes: icebreaker/, profile/, linkedin/, farcaster/, github/, twitter/. - connectedSocialPaths: search the network of the given handle(s), not the handles themselves. Pair with ordinality ["Global"] for that person's full indexed network. Up to 1000 paths per request, for example social_paths from get_team. - sortBy: "relevance", "trust_score", "connection_date", or "network_distance". The last two need viewer context. - allowAnyCredential: true matches profiles with ANY credential (OR), false matches ALL (AND). - connectionFollowType: "connection" (default when undefined), "recommendations", "following", or "follower". - Company by domain: append ["credentialnames:Verified: companydomain.com"] to globs. includeAssociations defaults to true (anyone associated with the company); set it to false only for verified members only. Both modes return current and past affiliation, with no current-only filter. For several companies at once, set allowAnyCredential true. - Do not put credentialNames into a plain glob; use the credentialnames:Verified: form above. FINDING ONE PERSON AT A COMPANY: do not glob the person's name and company together. Pull the company with globs=["credentialnames:Verified: <companydomain.com>"], paginate with offset until a page returns fewer than limit, then match the name yourself. A glob like ["Benjamin software engineer lazer technologies"] misses people whose titles are indexed differently. RECOMMENDED B…
upload_self_connections_csv
ChatGPTUpload your own LinkedIn Connections.csv onto your verified LinkedIn. csv_text is the raw file contents. You must already have a connected verified LinkedIn. teamDomainScope is optional and scopes the completed sync to that team.
upload_team_member_connections_csv
ChatGPTUpload a LinkedIn Connections.csv onto a team member's network. Use when an admin or collaborator on a paying team has that person's Connections.csv and wants those connections added to the member's LinkedIn network. target_social_path must start with linkedin/. teamDomainScope is required and is the team's domain. csv_text is the raw file contents. Call get_team_collaborators and pass that member's linkedin/ path.