Skip to main content
Glama

Searchapi

by io.searchapi
OverviewDiscussionsAdmin

Google Jobs

google_jobs
Read-only

Search for job listings on Google Jobs. Returns job postings with titles, company names, locations, descriptions, and apply links aggregated from multiple job boards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesJob search query (e.g., 'software engineer', 'data scientist in New York'). Required.
glNoCountry code for search context (e.g., 'us', 'gb'). Defaults to the country of `location`, otherwise us. Some countries return results in their local language.
pageNoDeprecated. Use `next_page_token` to request the next page.
latitudeNoLatitude of the search location, in decimal degrees (-90 to 90). Use with `longitude`. Cannot be combined with `location`.
locationNoLocation for job search (e.g., 'San Francisco, CA', 'London, United Kingdom').
longitudeNoLongitude of the search location, in decimal degrees (-180 to 180). Use with `latitude`. Cannot be combined with `location`.
next_page_tokenNoToken from `pagination.next_page_token` in the previous response. Retains the original search location.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / gl / description
      Previous value: -"Country code for search context (e.g., 'us', 'gb'). Default: us."New value: +"Country code for search context (e.g., 'us', 'gb'). Defaults to the country of `location`, otherwise us. Some countries return results in their local language."
  2. Changed4 schema fields changed
    • addedInput schema / properties / latitude
      Added value: +{
+  "description": "Latitude of the search location, in decimal degrees (-90 to 90). Use with `longitude`. Cannot be combined with `location`.",
+  "type": "number"
+}
    • addedInput schema / properties / longitude
      Added value: +{
+  "description": "Longitude of the search location, in decimal degrees (-180 to 180). Use with `latitude`. Cannot be combined with `location`.",
+  "type": "number"
+}
    • addedInput schema / properties / next_page_token
      Added value: +{
+  "description": "Token from `pagination.next_page_token` in the previous response. Retains the original search location.",
+  "type": "string"
+}
    • changedInput schema / properties / page / description
      Previous value: -"Page number for pagination. Default: 1."New value: +"Deprecated. Use `next_page_token` to request the next page."
  3. Changed1 schema field changed
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
  4. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already establish read-only and non-destructive behavior, so the description only needs to add useful context. It adds that results are aggregated from multiple job boards and lists returned fields, but it does not disclose pagination behavior or variable result availability. This is acceptable for a safe read-only search but the behavioral disclosure is modest.

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?

A single front-loaded sentence gives the purpose and output fields without any filler or repetition. It is appropriately sized for a search tool with a well-documented schema.

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?

With no output schema, the description supplies the main return contract (titles, companies, locations, descriptions, apply links). Parameter semantics are fully covered by the schema, including pagination via next_page_token, leaving only minor gaps such as result-count or error behavior.

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 covers all seven parameters with descriptions, so the parameter burden is already fully met. The tool description adds no parameter-specific semantics beyond the schema, which is fine given the 100% coverage baseline.

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?

States a specific verb-resource pair ('Search for job listings on Google Jobs') and enumerates the returned data (titles, company names, locations, descriptions, apply links). The vertical scope clearly separates it from generic siblings like bing_search, google_search_light, and other vertical search tools.

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?

The description gives a clear usage context: use it when job listings are needed, and it is explicitly scoped to Google Jobs and aggregated boards. It does not name an alternative or provide an explicit when-not, so it falls just short of full guidance.

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

All Searchapi toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources