Skip to main content
Glama

search_jobs

Read-onlyIdempotent

Find real-time public LinkedIn job listings without authentication and filter by keyword, location, experience, employment type, posting age, and remote status.

Instructions

Search real-time public LinkedIn job listings without authentication.

Returns deduplicated jobs with:

  • id: LinkedIn numerical job ID

  • t: Job title

  • co: Hiring organization name

  • loc: Job location

  • posted: Exact ISO date (YYYY-MM-DD)

  • age: Relative age (e.g. '2d', '1w')

  • benefits: Benefits badge (e.g. 'Actively Hiring')

  • sal: Salary range if published

  • relevance: Match percentage against search keyword (0-100%)

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

Input Schema

NameRequiredDescriptionDefault
kwYesTarget job title, skill, or role keyword (e.g. 'Python Backend Developer', 'DevOps')
ageNoPosting age filter: 'r86400' (past 24h), 'r604800' (past week), 'r2592000' (past month)
expNoExperience level code: 1=Internship, 2=Entry level, 3=Associate, 4=Mid-Senior, 5=Director, 6=Executive
locNoGeographic location or city (e.g. 'Chennai, India', 'Remote', 'Bengaluru')
typeNoEmployment type filter: 'fulltime', 'parttime', 'contract', 'internship'
limitNoMaximum number of unique job postings to return (1-100, default 20)
remoteNoSet to true for remote-only positions, false for onsite

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.4.8
    • addedInput schema / properties / age / description
      Added value: +"Posting age filter: 'r86400' (past 24h), 'r604800' (past week), 'r2592000' (past month)"
    • addedInput schema / properties / exp / description
      Added value: +"Experience level code: 1=Internship, 2=Entry level, 3=Associate, 4=Mid-Senior, 5=Director, 6=Executive"
    • addedInput schema / properties / kw / description
      Added value: +"Target job title, skill, or role keyword (e.g. 'Python Backend Developer', 'DevOps')"
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of unique job postings to return (1-100, default 20)"
    • addedInput schema / properties / loc / description
      Added value: +"Geographic location or city (e.g. 'Chennai, India', 'Remote', 'Bengaluru')"
    • addedInput schema / properties / remote / description
      Added value: +"Set to true for remote-only positions, false for onsite"
    • addedInput schema / properties / type / description
      Added value: +"Employment type filter: 'fulltime', 'parttime', 'contract', 'internship'"
  2. First observedv0.1.2

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavior beyond that: authentication is not required, results are deduplicated, and the relative age and relevance fields are explained. Rate limits and pagination behavior are still unstated.

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?

The main purpose is front-loaded in a single sentence, followed by a compact field list that is easy to scan. The return-field enumeration is somewhat verbose given that an output schema exists, but it remains useful and appropriately sized.

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

Completeness4/5

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

Given seven parameters, full schema coverage, annotations, and an output schema, the definition supplies the key missing context: no authentication needed, deduplication, and field meanings. The main gap is the absence of guidance on when to choose this tool over the other search_jobs variants.

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

Parameters3/5

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

Schema description coverage is 100%, so all seven parameters are already documented in the schema. The description does not add parameter-level meaning such as accepted keyword syntax or how filters combine, so it meets the baseline rather than exceeding it.

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?

The description states a specific verb and resource ('Search real-time public LinkedIn job listings') and adds an important qualifier ('without authentication'). It clearly identifies the tool as a job search, but does not differentiate it from siblings such as search_jobs_multi or search_jobs_advanced.

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?

It establishes context (public, real-time, no auth required) but gives no explicit when-to-use guidance, no exclusions, and no routing to alternatives. An agent must infer from sibling names which search variant is appropriate.

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