A
licenseB
qualityD
maintenanceA Model Context Protocol server that enables LLMs to perform web searches using Google's Custom Search API through a standardized interface.
1
47
MIT
Google Jobs MCP Server
by ChanMeng666
The Google Jobs MCP Server enables comprehensive job search functionality via the SerpAPI with various filtering options and multi-language support:
Query-based searches: Search using keywords or job titles like 'software engineer'
Location filtering: Specify locations and search radius (e.g., '10mi')
Date filtering: Filter by posting date (today, last 3 days, last week, last month)
Job type filtering: Find full-time, part-time, contract, internship, or temporary positions
Salary filtering: Filter by salary range (e.g., '$100K+')
Multi-language support: Display results in English, Chinese, Japanese, or Korean
Sorting options: Sort by date, relevance, or salary
Pagination: Navigate through results (10 per page)
Provides Google Jobs search capabilities through SerpAPI integration, allowing users to search for job listings with various filters including job title, location, employment type, salary range, and more.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Google Jobs MCP Serverfind software engineer jobs in San Francisco with remote options"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Google Jobs MCP Server
Job search for your AI assistant.
Ask Claude to find jobs. It searches Google Jobs and answers with real listings, each with a link to apply.
https://github.com/user-attachments/assets/8f6739e1-7db7-4171-88b4-59c6290a4c72
Try it
Get a key from SerpApi, then add this to claude_desktop_config.json:
{
"mcpServers": {
"google-jobs": {
"command": "npx",
"args": ["-y", "@chanmeng666/google-jobs-server"],
"env": { "SERP_API_KEY": "your-api-key" }
}
}
}Restart Claude and ask:
Find full-time data analyst jobs in Tokyo posted this week.
Related MCP server: Scrapeless MCP Server
Why use it
One tool to learn.
search_jobsneeds only a query. Add a location, radius, posting date, job type or salary to narrow it.Whole listings, not just titles. Each result has the company, location, posting time, job type, description and apply link, plus salary and benefits when the listing has them.
Four languages. Results can be labelled in English, Chinese, Japanese or Korean.
flowchart LR
Q([Your request]) --> C[Claude calls<br/>search_jobs]
C --> S[SerpApi<br/>Google Jobs]
S --> F[Server formats<br/>each listing]
F --> A([Answer with<br/>apply links])For your agent
This page is all a person needs. Everything else is written for agents: clone the repo and point yours at llms.txt and docs/overview.md.
git clone https://github.com/ChanMeng666/server-google-jobsFull overview · MCPB install guide · Changelog · Contributing · Security · MIT
See also: Google News MCP Server. Built by Chan Meng.
Available Tools
1 toolsearch_jobsB
Google Jobs API search tool.
Supported search parameters:
Basic Search: Job title or keywords
Location: City or region
Time Filter: Recently posted jobs
Job Type: Full-time, part-time, contract, internship
Salary Range: Filter by compensation
Geographic Range: Set search radius
Language: Multi-language support
All parameters except 'query' are optional and can be freely combined.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search keywords (Required, e.g., 'software engineer', 'data analyst', 'product manager') | |
| location | No | Job location (Optional, e.g., 'New York', 'London', 'Tokyo') | |
| posted_age | No | Posting date filter (Optional) Options: - "today": Posted today - "3days": Last 3 days - "week": Last week - "month": Last month | |
| employment_type | No | Job type (Optional) Options: - "FULLTIME": Full-time - "PARTTIME": Part-time - "CONTRACTOR": Contractor - "INTERN": Internship - "TEMPORARY": Temporary | |
| salary | No | Salary range (Optional) Format examples: - "$50K+": Above $50,000 - "$100K+": Above $100,000 - "$150K+": Above $150,000 | |
| radius | No | Search radius (Optional) Format examples: - "10mi": Within 10 miles - "20mi": Within 20 miles - "50mi": Within 50 miles | |
| hl | No | Result language (Optional) Options: - "en": English - "zh-CN": Chinese - "ja": Japanese - "ko": Korean | en |
| page | No | Page number (Optional, default: 1) - 10 results per page - Supports pagination | |
| sort_by | No | Sort order (Optional) Options: - "date": Sort by date - "relevance": Sort by relevance - "salary": Sort by salary | relevance |
TDQS
B3.2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It describes the search parameters and their optionality, which is useful, but it doesn't mention rate limits, authentication requirements, error handling, or what the output looks like (e.g., format, pagination details beyond '10 results per page' in the schema). For a tool with 9 parameters and no annotations, this leaves significant gaps in understanding its behavior.
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 description is appropriately sized and front-loaded, starting with the tool's purpose and followed by a structured list of parameters. Every sentence adds value, with no redundant information. However, the bulleted list could be slightly more concise, and the final sentence about optional parameters is necessary but adds length.
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?
Given the complexity (9 parameters, no output schema, no annotations), the description is partially complete. It covers the search parameters well but lacks details on behavioral aspects like rate limits, authentication, and output format. Without annotations or an output schema, the description should do more to compensate, but it provides a functional overview that is adequate for basic 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?
The schema description coverage is 100%, meaning all parameters are well-documented in the input schema itself. The description adds value by summarizing the supported search parameters in a bulleted list and noting their optionality, but it doesn't provide additional semantic context beyond what the schema already covers (e.g., no examples of combined usage). This meets the baseline for high schema coverage.
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 clearly states the tool searches for jobs using the Google Jobs API with specific search parameters. It provides a verb ('search') and resource ('jobs'), making the purpose immediately understandable. However, since there are no sibling tools mentioned, it doesn't need to differentiate from alternatives, so a 5 is not warranted.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage through the list of supported search parameters and notes that all parameters except 'query' are optional. This provides some context for when to use certain features, but it doesn't offer explicit guidance on when to use this tool versus alternatives (none mentioned) or any prerequisites. The guidance is functional but not strategic.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v1.0.0- First observed
search_jobs
TDQS
B3.3/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'search_jobs' has a clearly defined and distinct purpose for job searching.
Naming Consistency5/5
The tool name 'search_jobs' follows a consistent verb_noun pattern. Since there is only one tool, there is no inconsistency to evaluate, and the naming is straightforward and descriptive.
Tool Count2/5
A single tool is too few for a server named 'Google Jobs MCP Server', which implies a broader domain of job-related operations. While search is a core function, the lack of tools for actions like retrieving job details, applying, or managing saved jobs makes the set feel incomplete and thin.
Completeness2/5
The tool surface is severely incomplete for a jobs domain. It only provides search functionality, missing essential operations such as getting detailed job information, applying to jobs, saving or bookmarking jobs, or filtering by employer. This will likely cause agent failures when trying to perform common job-related tasks beyond basic searching.
Maintenance
ActivityMaintained
ResponsivenessNo issues
Related MCP Connectors
A Model Context Protocol server for Wix AI tools
MCP server for Google search results via SERP API
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Official SerpApi MCP server for Google, Bing, and other search engines.
Related MCP Servers
- AlicenseCqualityCmaintenanceA Model Context Protocol server implementation that enables AI assistants like Claude to perform Google searches and retrieve web data directly through natural language requests.179 npm169MIT
- FlicenseCqualityCmaintenanceA Model Context Protocol server that enables LLMs to perform Google searches via the Serper API, allowing models to retrieve current information from the web.1339-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants to perform web searches using Google Search API, returning up to 20 search results in JSON format.2Apache 2.0