LinkedIn Tools

This category is LinkedIn automation: 19 tools for searching companies, resolving people, fetching profiles, browsing posts and jobs, listing employees with boolean title filters, and sending DMs and invitations. The write and personal-data tools run on a logged-in session shared through the browser extension, so the same browser identity persists across calls.

Tools

Sessions: the browser extension

Write tools (send_linkedin_message, send_linkedin_invitation) and personal read tools (list_linkedin_conversations, list_linkedin_saved_posts, list_user_posts) need a logged-in LinkedIn session. That session is shared through the GTM Tools browser extension: install it, press Connect, and stay logged into LinkedIn in that browser. The extension syncs your session to your workspace and keeps it fresh automatically. Other read tools work without a session.

If you call one of these tools before connecting, it returns instructions with the install link. list_connected_linkedin_accounts shows which sessions are active; each teammate who connects adds theirs to a pool the tools rotate across.

Resolving identifiers

The most common pattern is domain → company URL → employees → profile.

$
# 1. Domain → company URL (2 credits)
$
curl -X POST https://api.gtm-tools.sh/api/v0/get_linkedin_company_url \
>
  -H "Authorization: Bearer $GTM_TOOLS_API_KEY" \
>
  -H "Content-Type: application/json" \
>
  -d '{"domain": "siena.cx"}'
$
$
# 2. Search employees with boolean title filters (30 credits)
$
curl -X POST https://api.gtm-tools.sh/api/v0/list_linkedin_company_employees \
>
  -H "Authorization: Bearer $GTM_TOOLS_API_KEY" \
>
  -H "Content-Type: application/json" \
>
  -d '{
>
    "domain": "siena.cx",
>
    "title_filters": "(VP OR Director OR Head) AND Sales NOT intern",
>
    "limit": 25,
>
    "page": 1
>
  }'
$
$
# 3. Get a profile URL from name + company domain (5 credits)
$
curl -X POST https://api.gtm-tools.sh/api/v0/get_linkedin_profile_url \
>
  -H "Authorization: Bearer $GTM_TOOLS_API_KEY" \
>
  -H "Content-Type: application/json" \
>
  -d '{"name": "Andrei Negrau", "domain": "siena.cx"}'
$
$
# 4. Get the profile (2 credits)
$
curl -X POST https://api.gtm-tools.sh/api/v0/get_linkedin_profile \
>
  -H "Authorization: Bearer $GTM_TOOLS_API_KEY" \
>
  -H "Content-Type: application/json" \
>
  -d '{"profile_url": "https://linkedin.com/in/andreinegrau"}'

list_ vs search_

Two tools answer “who works at this company?” with different cost/quality trade-offs:

Both tools accept the same domain, title_filters, limit, and page body. search_ does not take company_id.

All search_ fields (first_name, last_name, full_name, job_title, location, company_domain, linkedin_url) are labeled identically in list_, so an agent can read either response uniformly on that 7-field common set. list_ additionally exposes about and a stable RapidAPI profile_id. location is best-effort on search_ (Haiku reads it from SERP metadata when present, otherwise null).

Title filter syntax

Both list_linkedin_company_employees and search_linkedin_company_employees accept boolean expressions in title_filters:

The same syntax works in the CLI’s --filter flag.

Posts and engagement

list_linkedin_company_employees_posts is by far the most expensive LinkedIn tool because it fans out across employees. Prefer list_linkedin_company_posts (2 credits) when you only need official content, or scope to a known set of profile URLs with list_user_posts (5 credits each).

Jobs

Combine with signal_hiring_role (in Signals Tools) to confirm hiring activity from multiple sources.

Outreach

send_linkedin_invitation and send_linkedin_message write to LinkedIn through the connected session. Both require a LinkedIn session connected via the browser extension first.

$
curl -X POST https://api.gtm-tools.sh/api/v0/send_linkedin_invitation \
>
  -H "Authorization: Bearer $GTM_TOOLS_API_KEY" \
>
  -H "Content-Type: application/json" \
>
  -d '{
>
    "profile_url": "https://linkedin.com/in/andreinegrau",
>
    "message": "Hi Andrei, saw your post on CX agents. Would love to compare notes."
>
  }'

list_linkedin_conversations returns recent threads so your agent can poll for replies.

Next steps