Skip to main content
Glama

search_jobs_advanced

Read-onlyIdempotent

Search public LinkedIn jobs by keyword and filter by company, location, experience, remote status, and posting age; sort results by relevance or date.

Instructions

Advanced public LinkedIn job search with company filtering, date sorting, and relevance scoring.

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_advanced"
  }
}

Input Schema

NameRequiredDescriptionDefault
coNoFilter strictly by hiring company name
kwYesJob title, skill, or keyword search
ageNoAge filter: 'r86400' (24h), 'r604800' (week), 'r2592000' (month)
expNoExperience level: 1=Internship, 2=Entry level, 3=Associate, 4=Mid-Senior
locNoLocation, city, or 'Remote'
sortNoSort order: 'relevance' or 'date' (most recent first)relevance
typeNoEmployment type: 'fulltime', 'parttime', 'contract', 'internship'
limitNoMaximum number of job postings to return
remoteNoFilter for remote jobs

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.4.8
    • addedInput schema / properties / age / description
      Added value: +"Age filter: 'r86400' (24h), 'r604800' (week), 'r2592000' (month)"
    • addedInput schema / properties / co / description
      Added value: +"Filter strictly by hiring company name"
    • addedInput schema / properties / exp / description
      Added value: +"Experience level: 1=Internship, 2=Entry level, 3=Associate, 4=Mid-Senior"
    • addedInput schema / properties / kw / description
      Added value: +"Job title, skill, or keyword search"
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of job postings to return"
    • addedInput schema / properties / loc / description
      Added value: +"Location, city, or 'Remote'"
    • addedInput schema / properties / remote / description
      Added value: +"Filter for remote jobs"
    • addedInput schema / properties / sort / description
      Added value: +"Sort order: 'relevance' or 'date' (most recent first)"
    • addedInput schema / properties / type / description
      Added value: +"Employment type: 'fulltime', 'parttime', 'contract', 'internship'"
  2. First observedv0.1.2

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds that results come from public LinkedIn listings, but says nothing about pagination, result caps beyond the limit param, or failure modes such as empty/blocked responses.

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?

A single front-loaded sentence with no wasted wording; the feature list is compact. It is arguably too terse for a 9-parameter tool, but not padded.

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?

An output schema exists, so return values need not be explained, and the input schema is fully annotated. What is missing is routing context against the crowded sibling set of search tools, which for a 9-parameter 'advanced' variant is the main thing the description should have supplied.

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 every parameter is already documented in the schema, which sets the baseline at 3. The description only echoes co and sort semantics and says nothing extra about kw, age, exp, loc, type, limit or remote.

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 ('Advanced public LinkedIn job search') and names three differentiators: company filtering, date sorting, relevance scoring. However, 'advanced' is not defined relative to the close siblings search_jobs, search_jobs_multi and smart_match_jobs, so the agent cannot tell from the description alone which search tool to pick.

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?

The description gives no when-to-use guidance, no prerequisites (e.g., that it hits public LinkedIn listings), and no exclusions or alternatives. With several sibling search tools, silence on which one to choose is a real gap.

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