Google Jobs MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SERP_API_KEY | Yes | Your SERP API key obtained from the SERP API website |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_jobsB | Google Jobs API search tool. Supported search parameters:
All parameters except 'query' are optional and can be freely combined. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
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.
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.
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.
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.