Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

google_jobs

Search job postings by query, optionally filter by location, and paginate results to retrieve structured listings with title, company, employment type, and URL.

Instructions

Search Google Jobs. Searches Google Jobs for the query in the request body, optionally narrowed by location and paged with page. Each result has the job title, company, location, employment type, posting time, snippet, source and URL. The response echoes the query, location and page.

Input Schema

NameRequiredDescriptionDefault
optionYesGoogle Jobs search payload

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / option / properties
      Added value: +{
+  "location": {
+    "type": "string"
+  },
+  "page": {
+    "type": "integer"
+  },
+  "query": {
+    "type": "string"
+  }
+}
    • addedInput schema / properties / option / required
      Added value: +[
+  "query"
+]
  2. First observedv1.0.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full burden and does disclose the return shape (job title, company, location, employment type, posting time, snippet, source, URL) plus the echo of query/location/page and the fact that results are paged. It stops short of stating read-only nature, auth needs, or result-count/rate limits, so it is not fully transparent.

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?

Three tight sentences, front-loaded with the verb+resource and no filler. Minor redundancy in 'Search Google Jobs. Searches Google Jobs...' opening, but otherwise efficient.

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?

For a read-only search tool with no annotations, the description is adequate: it covers inputs and return fields. It is incomplete on sibling differentiation (google_jobs_search / google_jobs_job) and on any limitations of the search or pagination.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3, but the description goes beyond the schema by explaining semantics: query is the search subject, location optionally narrows it, and page paginates. That is real added meaning rather than restatement.

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?

States a specific verb+resource ('Search Google Jobs') and enumerates the result fields. However, it does not distinguish this tool from the closely named siblings google_jobs_search and google_jobs_job, which an agent could easily confuse it with.

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

Usage Guidelines2/5

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

No when-to-use guidance, no mention of alternatives, and no prerequisites or exclusions. The agent gets no help deciding between this, google_jobs_search, or google_jobs_job.

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

Deploy Server

Other Tools