Skip to main content
Glama
Servation

job-search-mcp

Find Jobs

find_jobs

Search live jobs from LinkedIn, Greenhouse, Lever, and other boards. Deduplicate results and return full descriptions with filters for role, location, experience, and job type, using your saved profile by default.

Instructions

Source live jobs (LinkedIn + Greenhouse, Lever, Ashby, Workday, SmartRecruiters, Hacker News, RemoteOK, Remotive), dedup them, and return them as text with full descriptions. Uses the saved profile's roles/location by default; pass query/location/filters to override. This returns UNSCORED jobs and does NOT show a card UI — immediately score all of them with evaluate_jobs (a 0-100 fit score + reason each), then show_board once, to present the single ranked board. Do not just list them back.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax jobs to return/persist this run (default 15).
queryNoRole/keyword filter, e.g. 'backend java spring'. Overrides the profile's target roles.
remoteNoWorkplace type (LinkedIn); also sets remote preference.
sort_byNoLinkedIn result ordering.
sourcesNoRestrict to these sources (default: all).
job_typeNoEmployment type (LinkedIn).
locationNoLocation filter, e.g. 'California' or 'Remote'. Overrides the profile's search location.
max_yearsNoCandidate's years of experience for this search (overrides the saved profile); also defaults the seniority filter.
salary_minNoMinimum annual salary filter (LinkedIn), e.g. 100000.
date_postedNoRecency filter (LinkedIn).
verify_urlsNoIf true, network-verify each job URL (slower). Default false.
max_applicantsNoSurface low-applicant LinkedIn jobs (uses LinkedIn's early-applicant filter, ~under 25). Exact applicant-count filtering requires the LinkedIn cookie.
experience_levelNoSeniority filter (LinkedIn).
Behavior4/5

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

With no annotations, the description covers key behaviors: dedup, returns text, no card UI, uses saved profile by default. It mentions verify_urls performance implication but lacks details on rate limits or auth. Overall transparent enough for agent decision-making.

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

Conciseness5/5

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

The description is concise—two sentences plus a workflow directive. It front-loads the purpose and packs necessary guidance without fluff. Every sentence adds value.

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 13 parameters, no output schema, and multiple siblings, the description adequately explains the tool's output format (text), the workflow, and default behavior. Could mention the default limit value (15) but schema covers it. Overall complete for practical use.

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 parameters are well-documented there. The tool description adds context about defaults and overrides, but this is minimal extra value. Baseline 3 is appropriate.

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?

The description clearly states it sources live jobs from multiple platforms, deduplicates them, returns text with full descriptions, and distinguishes its role from sibling tools like evaluate_jobs and show_board. It specifies the action and resource precisely.

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

Usage Guidelines5/5

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

The description provides explicit workflow instructions: the tool returns unscored jobs, and the agent must then call evaluate_jobs and show_board. It also explains how to override default profile settings. This clearly tells when and how to use the tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Servation/job-search-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server