Skip to main content
Glama
BACH-AI-Tools

bach-jsearch

Official

job_search

Find jobs on any public job site via Google for Jobs. Apply filters for location, employment type, posting date, remote work, and requirements to narrow results.

Instructions

Search for jobs posted on any public job site across the web on the largest job aggregate in the world (Google for Jobs). Extensive filtering support and most options available on Google for Jobs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage to return (each page includes up to 10 results). Default: 1 Allowed values: 1-501
queryYesFree-form jobs search query. It is highly recommended to include job title and location as part of the query, see query examples below. Examples: web development jobs in chicago marketing manager in new york via linkedin
fieldsNoA comma separated list of job fields to include in the response (field projection). By default all fields are returned. Example: employer_name,job_publisher,job_title,job_country
radiusNoReturn jobs within a certain distance from location as specified as part of the query (in km). This internally sent as the Google \\\"lrad\\\" parameter and although it might affect the results, it is not strictly followed by Google for Jobs.
countryNoCountry code of the country from which to return job postings. Please note that this parameter must be set in order to get jobs in a specific country, for example, to query for software developer jobs in Berlin, one should add country=de to the request - e.g. query=software+developers+in+berlin&country=de. Default: us Allowed values: See https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2
languageNoLanguage code in which to return job postings. Leave empty to use the primary language in the specified country (country parameter). Note that each country supports certain languages. In case a language not supported by the specified country is used, it is likely that no results will be returned. Allowed values: See https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes
num_pagesNoNumber of pages to return, starting from page. Default: 1 Allowed values: 1-50 Note: each 10 results page returned by the API will consume a single request from the quota.1
date_postedNoFind jobs posted within the time you specify. Default: all Allowed values: all, today, 3days, week, month
work_from_homeNoExample value:
employment_typesNoFind jobs of particular employment types, specified as a comma delimited list of the following values: FULLTIME, CONTRACTOR, PARTTIME, INTERN.
job_requirementsNoFind jobs with specific requirements, specified as a comma delimited list of the following values: under_3_years_experience, more_than_3_years_experience, no_experience, no_degree.
exclude_job_publishersNoExclude jobs published by specific publishers, specified as a comma (,) separated list of publishers to exclude. Example: BeeBe,Dice
Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It notes 'most options available on Google for Jobs' which hints at limitations, but it does not mention pagination, quota consumption, read-only nature, or result format. This is a significant gap for an unannotated tool.

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?

Two sentences, no redundancy, front-loaded with the core action. Efficient.

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

Completeness2/5

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

The tool is complex (12 params) and lacks an output schema, and the description does not explain return values or how results relate to sibling tools. Despite rich schema, the description alone leaves the agent without a clear picture of expected output or limits.

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 coverage is 100%, with each parameter documented in detail (e.g., query examples, allowed values, defaults). The description adds no parameter-specific semantics beyond stating extensive filtering, so baseline 3 applies.

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 'Search for jobs posted on any public job site across the web' with the specific resource (jobs) and scope (Google for Jobs aggregate). It effectively distinguishes job_search from sibling tools (job_details, job_salary) which focus on specific job info.

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

Usage Guidelines4/5

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

It establishes that this tool is for searching job listings and highlights extensive filtering, which implies use for discovery. However, it does not explicitly name when to prefer siblings or when-not, though the context is reasonably clear.

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/BACH-AI-Tools/bachai-jsearch'

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