Skip to main content
POST
List LinkedIn Team Connections

Authorizations

X-API-Key
string
header
required

Body

application/json
mode
enum<string> | null

Lookup mode.

  • Omit or set auto for all known team connections, or when filters make the intent obvious.
  • Use connections_of_team_member for 'show Michael's connections'.
  • Use team_members_connected_to_person for 'who on our team is connected to Michael'.
Available options:
auto,
connections_of_team_member,
team_members_connected_to_person,
null
ownerUserId
string | null

FirstTouch team member user id whose LinkedIn account owns the relation list. Use for connections_of_team_member, or to narrow team_members_connected_to_person.

ownerSearch
string | null

Search team member/account owner by name, email, LinkedIn account name, or LinkedIn public identifier. Example: Michael Kurson.

linAccountId
string | null

Exact FirstTouch LinkedIn account id to read or narrow by.

connectedPersonLinkedInUrl
string | null

Connected person's LinkedIn profile URL.

connectedPersonPublicIdentifier
string | null

Connected person's LinkedIn public identifier, for example michael-kurson.

connectedPersonName
string | null

Connected person's first name, last name, or full name. Example: Michael Kurson.

searchQuery
string | null

Generic search over saved connected-person name, headline, LinkedIn URL, and public identifier.

headlineKeywords
(string | null)[] | null

Use for requests about the type of connection rather than a known individual: role, job title, profession, department, or specialty.

  • First extract the role-bearing word or phrase; generic group nouns such as person, people, contact, connection, and list are not search keywords.
  • When the user asks for 'Sales Persons', 'people in sales', 'CFOs', 'marketing leaders', or 'React developers', populate this argument before calling; do not issue an unfiltered request.
  • Supply up to nine precise literal title alternatives plus one broad, meaningful role fallback, with ten keywords maximum.
  • A connection matches when its saved headline contains any alternative, case-insensitively.
  • Put the user's direct phrase first because it ranks ahead of alternative-only matches, and put the broad fallback last.
  • For 'Sales Persons', sales is the role-bearing term and the array MUST include 'sales', not only 'salesperson'.
  • Example: ['sales person', 'salesperson', 'sales agent', 'sales representative', 'account executive', 'business development representative', 'sales'].
  • Do not submit weak standalone words such as 'person', 'manager', or 'director'.
  • Include an acronym only alongside its expanded title.
  • Leave mode as auto unless also narrowing by an owner.
  • Do not put these alternatives in searchQuery; searchQuery is a separate generic literal filter and combines with this filter.
connectedFromUtc
string<date-time> | null

Inclusive lower bound for when the LinkedIn connection was made, in ISO 8601 UTC form with an explicit offset.

  • Use this when the user asks for connections from/since a date or period.
  • For 'last week', use the prior Monday at 00:00 UTC.
  • Connections without a saved LinkedIn connection date are excluded when this filter is used.
connectedToUtc
string<date-time> | null

Exclusive upper bound for when the LinkedIn connection was made, in ISO 8601 UTC form with an explicit offset.

  • Use with connectedFromUtc for a period.
  • For 'last week', use the current Monday at 00:00 UTC.
  • Connections without a saved LinkedIn connection date are excluded when this filter is used.
limit
integer | null

Maximum rows to return. Defaults to 20, max 100.

cursor
string | null

Pagination cursor returned by a previous list_linkedin_team_connections response.

Response

Tool result.

summary
string
required
mode
enum<string>
required
Available options:
auto,
connections_of_team_member,
team_members_connected_to_person
connections
object
required
warnings
string[]
required
nextSteps
string[]
required