Skip to main content
Glama
LinkedIn Jobs MCP Server

LinkedIn Jobs MCP Server

Search Jobs

search_jobs
Read-only

Search LinkedIn job postings by keywords and filters, returning job IDs for full details; if filters drop, include location or work type in keywords.

Instructions

Search for jobs on LinkedIn.

Returns job_ids that can be passed to get_job_details for full info.

LinkedIn is moving accounts to a redesigned job search, which keeps only the keywords, date_posted and paging. It drops the filters marked "Classic search only" and reports them in section_errors as filters_dropped. When it drops the location or work type, search again with them in the keywords ("remote python developer in Lyon") and keep doing so; words such as "senior" or "internship" there narrow the results too. Quotes do not make a phrase exact on that search.

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": {
      "keywords": "<keywords>"
    },
    "name": "search_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
sort_byNoSort results (date, relevance). Classic search only.
job_typeNoFilter by job type, comma-separated (full_time, part_time, contract, temporary, volunteer, internship, other). Classic search only.
keywordsYesSearch keywords (e.g., "software engineer", "data scientist")
locationNoOptional location filter (e.g., "San Francisco", "Remote"). Classic search only.
max_pagesNoMaximum number of result pages to load (1-10, default 3)
work_typeNoFilter by work type, comma-separated (on_site, remote, hybrid). Classic search only.
easy_applyNoOnly show Easy Apply jobs (default false). Classic search only.
company_idsNoOptional numeric LinkedIn company IDs, comma-separated. Classic search only.
date_postedNoFilter by posting date (past_hour, past_24_hours, past_week, past_month)
distance_kmNoOptional search radius around location in kilometres (0-100). Classic search only.
experience_levelNoFilter by experience level, comma-separated (internship, entry, associate, mid_senior, director, executive). Classic search only.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.30.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses that the redesigned search ignores all filters marked "Classic search only", surfaces them as filters_dropped in section_errors, that keywords double as soft filters for seniority/role words, and that quotes do not create exact phrases. Those are non-obvious runtime behaviors an agent would otherwise get wrong.

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

Conciseness4/5

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

Front-loads purpose and return value, then the redesign caveat. Mostly tight, though the fallback instruction ("keep doing so") is slightly vague and the final two sentences could be merged without loss.

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

Completeness5/5

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

For an 11-parameter, open-world search with full schema coverage, an output schema, and annotations, the description covers the one thing structured fields cannot: the redesigned-search degradation and how to recover from it. Nothing needed to invoke it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning about the keywords parameter (that seniority words inside it narrow results and quoted phrases are not exact) and explains the practical consequence of the "Classic search only" marker on the other filters. It does not explain max_pages or date_posted behavior beyond the schema.

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

Purpose5/5

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

States a specific verb and resource ("Search for jobs on LinkedIn") and immediately clarifies the output contract ("Returns job_ids that can be passed to get_job_details"), which distinguishes it from the sibling that fetches full details.

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

Usage Guidelines4/5

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

Gives concrete operating guidance: use it to get job_ids, then hand off to get_job_details, and re-run the search with location/work type folded into keywords when the redesigned search drops filters. It lacks an explicit statement of when not to use it (e.g. saved jobs), but the alternative it points to is named.

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