LinkedIn for AI Agents

The job surface runs end to end. Your agent searches public listings with search_jobs, narrows them with filter_jobs (recency codes for past day, week, or month, plus on-site, remote, or hybrid work types), pages deeper with next_page, and opens a posting with view_job. On a job it can expand the collapsed description, save the job to your My Jobs list, and later read that list back with list_saved_jobs.

For Easy Apply jobs, apply_to_job opens the wizard in place, read_application_step reports the current step and any inline validation errors, fill_contact_info fills the commonly empty phone field, and continue_application advances step by step. The flow deliberately stops at LinkedIn's Review screen (see quirks below).

The social surface needs your signed-in session. search_people searches all of LinkedIn, search_connections scopes to your own first-degree network, and search_companies finds company pages. From there your agent opens profiles with view_profile, lists a company's staff with list_company_employees, checks your own profile with view_my_profile, and sends real connection requests with connect or connect_with_note.

Job search is public. search_jobs, filter_jobs, list_jobs, view_job, next_page, expand_description, and go_back_to_listing all work on LinkedIn's logged-out guest surface, no account needed.

The social and application surface requires a signed-in session: people and company search, profiles, connections, the feed, saving jobs, and the whole Easy Apply flow. The auth config points at linkedin.com/login, and the login action takes a username, password, and an OTP for two-step verification. The session rides LinkedIn's li_at cookie, and a capture_login flow connects your own account. If the session expires, LinkedIn redirects the feed and profile pages to its sign-in wall; actions like go_to_feed and view_my_profile detect this and report that the session needs reconnecting instead of failing silently.

These come straight from the mapped behavior, not guesswork:

• **Never fabricate a job or profile URL.** Job links must come from a url returned in data.listings; profile links must come from a prior search_people or search_connections result. The guest job results page can hide every per-job link behind a sign-in interstitial, and a hand-built /jobs/view/{id} link can send you to the wrong posting. The actions enforce this rule.
• **Guest search encoding matters.** Spaces in keywords and location must be %20-encoded, never +-encoded; a literal + silently degrades the match to a far broader result set. A contextual sign-in dialog can also cover fresh result pages; the config dismisses it automatically before reading.
• **Pagination is infinite scroll.** next_page auto-appends roughly 10 more results via XHR. Track growth through listings_total, not the length of data.listings, which stays pinned to a preview of the first page.
• **Irreversible writes are guarded.** submit_application is a canary: it advances to LinkedIn's Review screen and stops, never clicking Submit; you file the application yourself, or the agent calls discard_application to clean up. Likewise connect and connect_with_note send real invitations, require the member's exact display name from the profile top card, and back off when LinkedIn shows a weekly-invitation-limit dialog. Jobs that apply through an external company site are handed back to you rather than attempted.

The core reads return structured records. Job searches land on the guest results screen and list_jobs returns rows of {title, url, location, posted}. People searches return {name, profile_url, headline}; on search_connections, genuine first-degree connections carry a 1st marker in the headline, and the config tells agents to exclude LinkedIn's mixed-in suggested profiles. Company search returns {name, company_url, summary} with an industry, location, and size line, and view_company surfaces the HQ, follower line, and size band. Saved jobs come back as {title, url, meta}, where each url feeds directly into view_job and meta is a single text line packing company, location, posted age, and apply type that your agent parses out itself.

Behind those reads sit dedicated screens for the job detail page, the Easy Apply wizard, profile detail, company pages, people and company search, saved jobs, and the feed, so the agent always knows which surface it is on.