Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search LinkedIn jobs

linkedin_live_jobs_search_v2
Read-onlyIdempotent

Search LinkedIn job listings by keyword, location, salary, job type, and other filters to find matching roles; use the cursor to retrieve paginated results.

Instructions

Search LinkedIn jobs by keyword and filters. Optional inputs: count, start, cursor, keyword, sortBy and 16 more. Returns a list (use cursor when paginated).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "linkedin_live_jobs_search_v2"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo
startNo
cursorNo
salaryNo
sortByNorelevance
titlesNo
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
keywordNo
benefitsNoComma-separated, any of: `medical_ins`, `dental_ins`, `vision_ins`, `401k`, `pension`, `paid_maternity`, `paid_paternity`, `commuter`, `student_loan`, `tuition`, `disability_ins`.
jobTypesNoComma-separated, any of: `full_time`, `part_time`, `contract`, `temporary`, `internship`, `volunteer`, `other`.
companiesNo
easyApplyNoAccepts a native boolean, or the string `true`/`false`/`1`/`0` (case-insensitive).
functionsNo
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
locationsNoOne numeric LinkedIn geo ID for where the job is, e.g. `103644278` (United States) or `102257491` (London). Place names are not accepted; send one request per location. [Find a geo ID](https://www.socialfetch.dev/docs/api/v2/linkedin/geo-ids). Cannot be combined with `functions`, `titles`, `benefits`, `commitments`, `verifiedJob=true`, `fairChance=true`, the `volunteer` and `other` job types, or salaries other than `40k`, `60k`, `80k`, `100k`.
datePostedNo
experienceNoComma-separated, any of: `internship`, `entry_level`, `associate`, `mid_senior`, `director`, `executive`.
fairChanceNoAccepts a native boolean, or the string `true`/`false`/`1`/`0` (case-insensitive).
industriesNo
commitmentsNoComma-separated, any of: `dei`, `environmental`, `work_life`, `social_impact`, `career_growth`.
verifiedJobNoAccepts a native boolean, or the string `true`/`false`/`1`/`0` (case-insensitive).
workplaceTypesNoComma-separated, any of: `onsite`, `remote`, `hybrid`.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.
under10ApplicantsNoAccepts a native boolean, or the string `true`/`false`/`1`/`0` (case-insensitive).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive behavior, so the safety profile is covered. The description adds only that the result is a list and that pagination is cursor-based, which is modest value. It says nothing about result caps, credit/rate costs, or the fact that the schema is heavily filtered (locations constraints), despite being an open-world search tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded with the core purpose, but the second sentence enumerates five parameter names followed by 'and 16 more', which is filler that does not help an agent. That enumeration fails to earn its space and would be better replaced by usage or constraint information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 24-parameter, open-world search with no output schema, the description is thin: it never mentions the required context and llm_model parameters, the conversation_id handshake that forbids parallel calls, or the combinatorial restrictions on locations. The annotations and rich schema fields carry much of the burden, but the definition itself does not round out the picture.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 54% across 24 parameters, so the description should compensate — instead it names six parameters and dismisses the rest with 'and 16 more', which conveys no meaning. Critical semantics such as the required context/llm_model, conversation_id echo sequencing, and the many mutual-exclusion rules are left entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — 'Search LinkedIn jobs by keyword and filters' — which cleanly separates it from single-entity siblings such as linkedin_live_job_get_v2 or linkedin_live_organization_jobs_v2. It stops short of naming any sibling or scope boundary explicitly, so it is clear but not differentiating in the text itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this search versus linkedin_live_organization_jobs_v2, linkedin_live_job_similar_v2, or the non-LinkedIn job search siblings. The only operational hint is the parenthetical 'use cursor when paginated', which is a mechanics note rather than usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools