add_company_to_target_list
ChatGPTAdd one existing company to one target list owned by the connected user. Use only when the user asks to add the company. Resolve targetListId with list_target_lists and companyId with search_companies; use get_target_list when current membership is needed. Accepts the returned Homie id or LinkedIn companyId. Does not create or rename a list, create a company, remove members or send messages. If already present, returns changed:false. Requires a user-scoped MCP token with mcp:write; organization API keys and other users' lists are rejected.
add_prioritized_connection
ChatGPTAdd one of the authenticated user's own first-degree connections to their prioritized list, meaning the people they consider key relationships. This is a WRITE: it adds a strong priority signal to that connection's warmness score (recalculated immediately), moves the person to the top of the priority list, and, if that person also has a Homie account, promotes them to an accepted advocate so they appear as an available connector. Only call it when the user explicitly asks to prioritize, star, or flag someone; do not call it to 'improve' scores on your own initiative. Identify the person with personId (the id returned by list_first_degree_connections, search_people, or get_person); connectionId is accepted as an alternative for ids that came from a ghost opportunity's bestPath. Only the user's own first-degree connections can be prioritized, so second-degree people are rejected. Calling it again after it is at the top is a no-op and returns alreadyPrioritized: true. Requires a user-scoped MCP token; organization API keys are not supported.
check_warmness_rescore
ChatGPTReturn the current status and any persisted results from a background AI warmness re-scoring run queued by search_warm_paths or list_person_network. This check returns immediately and never waits for the AI worker. Use it only when the user later asks for an update; 'running' means calculation continues in the background, 'completed' means results are final, and 'none' means there is no recent run. Reads the caller's most recent run; pass runId only to target a specific one. User-scoped (needs a user MCP token).
create_target_list
ChatGPTCreate a new, empty target list owned by the authenticated user. This is a WRITE: only call it when the user explicitly asks for a new list, or when they ask to add companies to a list that does not exist yet (check with list_target_lists first). If the user already owns a list with exactly this name, no duplicate is created and that list is returned with created: false, so retries are safe. Follow up with add_company_to_target_list to add companies. Requires a user-scoped MCP token; organization API keys are not supported.
deprioritize_connection
ChatGPTMark one of the authenticated user's own first-degree connections as someone Homie should no longer recommend as a warm path. Use only when the user says the relationship is no longer warm, has a conflict, or should not be suggested. Identify the person with personId or connectionId, and optionally preserve the user's explanation in reason. Repeating the call updates the existing mark instead of creating another one; omitting reason preserves any explanation already stored. The mark removes an existing prioritization but does not rewrite the connection's underlying warmness score except to withdraw a removed priority boost. To see marks and their reasons use list_deprioritized_connections; to undo one use remove_deprioritized_connection. Requires a user-scoped MCP token with mcp:write; organization API keys, second-degree people, and other users' connections are rejected.
find_paths_to_person
ChatGPTStart a LinkedIn search for paths to ONE specific person the user wants to reach, through their own network. Use it when search_warm_paths found no warm path to that person, or the user asks to search LinkedIn for routes to them; use search_warm_paths first for the routes Homie already knows. Identify the person with personId (from search_people, get_person or search_warm_paths) or with the LinkedIn profile URL the user gave; never invent a URL, and never pass only a name: for a name, call search_people first or ask for the URL. It runs on the user's Homie extension and takes minutes. New paths are emailed to the user (and sent to their Slack DM when it is on) as they arrive, and the path to this person is sent even when it is cold or they are outside the ICP. A person searched in the last day is reported instead of searched again; pass rerun: true only when the user asks to search again. A first-degree connection needs no search. Requires a user-scoped MCP token with mcp:write.
get_company
ChatGPTFetch one company from Homie's directory by id. Accepts either the Homie company id (the id field) or the LinkedIn company id (the companyId field), both as returned by search_companies, get_target_list, or a person's currentCompany. Returns name, industry, headquarters, size range, and logo. This is a directory lookup, not a warm-path search; use search_warm_paths with prospectCompany to reach people there. Returns found: false when the id is unknown.
get_icp
ChatGPTUse this when the user asks for their ideal customer profile, open-ended sales prospecting ('who should we sell to?'), or customer qualification. Returns target positions, industries, locations, company sizes/types and descriptive context. Read before qualifying prospects; explicit user criteria override defaults. Warmness measures reachability, not customer fit. Do not require this for reaching an already chosen company/person, exploring connections, or finding investors, hires, job referrals, partners or experts. Org-scoped: supports user MCP tokens and organization API keys. If configured:false, ask for criteria only when the user has not already supplied them; do not block a fully specified search.
get_path_details
ChatGPTUse this when the user wants the numbers behind one introduction route from a search_network result: how warm each hop is and why (mutual connections, years worked or studied together, emails, meetings, reactions, and each factor's score). Pass the result's person id as targetPersonId and copy that result's chosen connectionSources entry into route (type, advocatePersonId, teamMemberId). Pass the same asUserId as the search when one was used. Returns each hop's stored warmness, readable signals and the full stored factor breakdown. One route per call: fetch details only for the routes the user asks about, never for every result. found:false means the route cannot be verified for this organization.
get_person
ChatGPTUse this when expanding a returned person for a meeting brief, connector context, role/company details or relationship evidence. Requires a real Homie person id from search_people, search_warm_paths or connection results; resolve a name with search_people first. Returns profile fields, current company, network size and available organizational warmness/signals. This is not an inbox, calendar, contact-history or live employment lookup. Only works for people in the organization's network (1st or 2nd degree); returns found:false otherwise.
get_target_list
ChatGPTRead one of the authenticated user's target lists and page through its matched companies. The summary also reports unmatchedCompanyCount for imported names not yet linked to a Homie company record. Use this to inspect membership before add/remove changes. Requires a user-scoped MCP token; organization API keys are not supported. Default limit 20, max 50; page with nextOffset.
list_deprioritized_connections
ChatGPTList the authenticated user's own deprioritized first-degree connections: people they asked Homie to stop suggesting as warm paths or connectors, with the reason they gave (notes, null when none) and when the mark was set or last updated. Newest first. Use it when the user asks who they have hidden or why someone is not being suggested, then remove_deprioritized_connection to restore one. Teammates' marks are private and never listed. Requires a user-scoped MCP token; organization API keys are not supported. Default limit 20, max 50; page with nextOffset.
list_first_degree_connections
ChatGPTList the authenticated user's own first-degree LinkedIn connections with offset pagination. Each entry is person fields only: id, name, linkedinId, position, currentCompany. This is your personal network as synced to Homie — for searching across the whole organization's network use search_people or search_network instead. Requires a user-scoped MCP token; organization API keys are not supported. Default limit is 20; pass limit up to 50 for more. To fetch the next page, call again with the nextOffset value returned in the previous response.
list_person_network
ChatGPTUse this when the user asks 'who does Alex know?', 'explore her network', or 'who could this adviser introduce us to?'. Lists a person's observed connections, warmest first, with profile fields and relationship signals. Use directly for network exploration; no sales ICP or ghost-opportunity prerequisite. search_sales_opportunities matches prospect fields, not connector identity. Identify the person by name, linkedinId or a returned personId; clarify ambiguous identities. The person must be an org member or a member's direct contact. Do not pass a non-member to search_network's asUserId. People with an already-requested intro are excluded and counted in excludedIntroRequested; includeIntroRequested:true brings them back annotated. Check coverage: synced = their imported network; derived = the indirectly observed slice; none = not mapped, never 'they know nobody'. With a user token, up to ten low-score edges may automatically be queued for background AI rescoring, which persists updated warmness scores and breakdowns. Answer immediately with current evidence, and use check_warmness_rescore only if the user later asks for an update. Org-scoped. Default limit 20, max 50; paginate with nextOffset.
list_sales_opportunities
ChatGPTList stored sales prospects recommended by Homie for the connected organization, with customer-profile fit, buying-intent signals and available introduction paths. Use for recommended leads, saved prospects or introductions already requested. Choose sort relevancy for best customer fit, newest for recent recommendations, or status intro_requested for existing intro requests. Filter by status or substring search on prospect name, company and position. Reads existing recommendations; it does not discover new prospects, change opportunities, send messages or represent a complete CRM. Default limit 20, max 50; paginate with nextOffset.
list_second_degree_connections
ChatGPTList the authenticated user's second-degree network: people connected to one of your own first-degree contacts, but whom you don't know directly. Each entry names the bridging connector (viaConnector) and the warmness on the connector→person edge, so you can see who could introduce you. Ordered warmest first. Pass viaConnectorId (a person id from list_first_degree_connections) to narrow to that connector. Coverage is bounded: totalCount counts people within the scanned window (not the entire network), and capped: true means bridge or per-connector edge limits were reached. Requires a user-scoped MCP token; organization API keys are not supported. Default limit 20, max 50; page with nextOffset.
list_target_lists
ChatGPTList the authenticated user's own target lists, most recently updated first. Returns each list's id, name, matched company count, unmatched imported-company count, and timestamps. Use this before rename_target_list, add_company_to_target_list or remove_company_from_target_list to resolve the targetListId. Requires a user-scoped MCP token; organization API keys are not supported.
remove_company_from_target_list
ChatGPTRemove one company's membership from one target list owned by the connected user. Use only when the user asks for this removal. Resolve targetListId with list_target_lists and companyId with search_companies; use get_target_list when current membership is needed. Accepts the returned Homie id or LinkedIn companyId. Does not delete the company or list, rename the list or remove other members. If already absent, returns changed:false. Requires a user-scoped MCP token with mcp:write; organization API keys and other users' lists are rejected.
remove_deprioritized_connection
ChatGPTUndo deprioritize_connection for one of the authenticated user's own first-degree connections, so Homie may suggest them as a warm path and connector again. Use when the user says they reconnected, the conflict is gone, or they want the person back. This only removes the mark: it does not prioritize them (use add_prioritized_connection for that) and does not change warmness. The response returns the reason that was stored on the removed mark. Calling it for someone who is not deprioritized is a no-op that returns removed: false. Identify the person with personId or connectionId. Requires a user-scoped MCP token with mcp:write; organization API keys, second-degree people, and other users' connections are rejected.
remove_prioritized_connection
ChatGPTRemove one of the authenticated user's first-degree connections from their prioritized list. This is a WRITE and the inverse of add_prioritized_connection: it withdraws the priority signal from that connection's warmness score (recalculated immediately). It does not revoke advocate status that was granted when the person was prioritized. Only call it when the user explicitly asks to unprioritize, unstar, or unflag someone. Identify the person with personId or connectionId, exactly as for add_prioritized_connection. Calling it for someone who is not prioritized is a no-op and returns removed: false. Requires a user-scoped MCP token; organization API keys are not supported.
rename_target_list
ChatGPTRename one target list owned by the connected user to the requested name. Use only when the user asks to rename it. Resolve targetListId with list_target_lists first. Does not create a list or change its company membership. Repeating the same name returns changed:false. Requires a user-scoped MCP token with mcp:write; organization API keys and other users' lists are rejected.
search_companies
ChatGPTLook up company records in Homie by name, industry, or HQ location. Use to resolve a company ID for a target list or expand company details. For who we know at a company or a way to reach its employees, use search_warm_paths instead.
search_network
ChatGPTUse this when the user wants a set of people to approach: sales prospects, design partners, investors to pitch, candidates to recruit, advisers/experts, agencies/providers, distribution partners, journalists, speakers or podcast guests. Examples: 'Which seed investors should I pitch?', 'find a founding engineer we could hire', 'who could advise us on enterprise sales?', 'who should I meet in Helsinki?', or 'scan our network for fintech CTOs'. No Homie or network keyword is required when actual people are requested. Searches existing professional contacts using natural-language criteria; general fundraising advice, a job description, company facts or technical-network scans do not need this tool. Preserve the user's criteria. Read get_icp for sales qualification; do not impose sales ICP on other goals. Profile matches do not establish availability, investment interest, attendance, past employment or willingness to help. For a named company/person use search_warm_paths instead. Personal-only search uses networks ['user']; default includes all permitted networks. This does not start a crawler, import data or create opportunities. No pagination or aggregate network analytics; results are limited to the requested count.
search_people
ChatGPTUse this when looking up a known contact by name/email, disambiguating a person or resolving an ID before a profile brief or explicit relationship change. Substring matches name, email, position and current company across the organization's first- and second-degree network. Use search_network for natural-language role/location/industry criteria and search_warm_paths for an introduction to someone. Each result includes degree ('first' or 'second'); first means direct to someone in the organization, not necessarily the current user. A current-company match does not establish previous employment.
search_sales_opportunities
ChatGPTSearch stored sales prospects recommended by Homie for the connected organization. Match query against prospect name, company and position; return existing recommendations with customer-profile fit, buying-intent signals and available introduction paths. Results sort by relevancy by default. Use for finding recommendations at a company or matching a role. This is a read-only search: it does not scan the whole network, discover or change opportunities, or send messages. Use search_network for broader prospecting and search_warm_paths for an introduction to a specific person or company. Default limit 20, max 50; paginate with nextOffset.
search_warm_paths
ChatGPTUse this when the user wants to reach a named company or person: "How can I reach Stripe?", "get me a meeting with [company]", "who do we know at X?", "reach their CFO", a job referral, an introduction to an investor/partner/journalist, or relationship context before meeting someone. Also use for comparing routes into specified accounts and contextual follow-ups. No Homie, network or intro keyword is required. A company request maps to prospectCompany with organization scope; prospectRoles narrows only roles the user requested. A known sales target does not require ICP qualification before finding a route. For an open-ended set of people to approach, use search_network. Public support/contact details, product login, directions and general company research alone do not need private network data. With a user token, low-score connections may automatically be queued for background AI rescoring (up to ten per call), which persists updated warmness scores and breakdowns. Return current evidence without waiting; use check_warmness_rescore only if the user later asks for an update. Connector responses are compact: raw factor breakdowns and image URLs are omitted; scores, hop signals and identities are retained. Pages fit a 12 KB JSON budget and may contain fewer paths than limit; always paginate with nextOffset, never offset + limit. For a named company, use one organization-scoped call for all permitted teammates; do not loop through members with search_network/asUserId. Find warm intro paths to exactly one target person OR company. By default it searches from everyone in the organization; narrow the source with scope or fromUserIds, and narrow how the target is reached with connectionTypes. Each path includes warmness scores and human-readable signal labels showing the relationship evidence. Pass prospectPersonId, prospectLinkedinId, prospectName (optionally with prospectCompany for disambiguation), or prospectCompany. Common scopings: my own network only = scope 'me'; paths through my first-degree connections = scope 'me' + connectionTypes ['second_degree']; people I already know directly = scope 'me' + connectionTypes ['direct']; a specific colleague's network = fromUserIds ['<their user or person id>']. In company mode, people the organization has already requested an intro to are excluded and counted in excludedIntroRequested; in person mode nothing is filtered, but the prospect is annotated with introRequested. Always inspect coverage.capped: a true value means bounded employee or graph scans may have omitted paths. Warmness says who is reachable, not who is worth reaching, so call get_icp first when prospecting and rank the results against it. Default limit is 20; pass limit up to 50 when the user asks for more paths. To fetch more results, call again with the nextOffset value returned in the previous response (or any explicit offset). Read outcome: found means at least one genuinely warm route (warmness > 0) was returned; no_paths means the target is reachable-in-name-only with no warm route; target_not_found means no such person/company is in the org's network. A no_paths result may still carry paths — cold routes whose connector→target hop scores 0 — so a path list alone is NOT proof of a warm route; always inspect each path's own warmness and null hop scores before calling it a warm intro, especially with includePossiblePaths. On no_paths/target_not_found the result carries a human-readable message and, when the org has any warm contacts, fallbackConnections — the organization's warmest reachable people as alternative starting points. Relay the message and offer the fallbacks as the org's closest existing contacts; never present them as a path to the requested target, and never report an empty result as 'they know no one'.