Icebreaker

List 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_lists_tool

Lookup 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.

lookup_viewer_tool

Create 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}

manage_list_tool

Return 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_entitlements_tool

Queue 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.

queue_network_sync_tool

Read 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_status_tool

Search 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 BY MY TEAM: connectionFollowType "recommendations" with either teamCollaborators "verified" or "collaborators" plus teamDomain, or connectedSocialPaths set to the team's social paths from get_team. Example: {"connectionFollowType": "recommendations", "teamCollaborators": "verified", "teamDomain": "acme.com", "globs": ["engineer"], "ordinality": ["1st", "2nd"], "limit": 50, "hideViewer": true}. TEAM REACH: call get_team for social_paths, then search with connectedSocialPaths set to that list. Read the total from response.hits.total when present, otherwise use total_results and paginate. If search results look thin, tell the user they can connect more accounts at https://app.icebreaker.xyz/settings/linked-accounts For the onboarding overview, call get_server_instructions.

search_network

Upload 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.

upload_team_member_connections_csv

Upload 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_self_connections_csv