Skip to main content
Glama
scraperapi

scraperapi-mcp-server

Official

google_jobs

Read-onlyIdempotent

Retrieve structured job postings (title, company, location, posting age, source) from Google Jobs widget based on a search query.

Instructions

Retrieve parsed Google Jobs listings for a query.

    Returns structured job postings (title, company, location, posting age,
    source) from the Google Jobs widget for a query.

    When to use:
    - Aggregating job listings for a role, company, or location
    - Labor-market or hiring research

    When NOT to use:
    - General web or news results (use 'google_search' / 'google_news')

    Args:
        params (GoogleJobsParams): query (required) plus optional localization
            (country_code, gl, hl, uule), pagination (num, start), tld, and
            output_format.

    Returns:
        str: JSON (default) or CSV containing the structured job listings.

    Raises:
        ToolError: If the API key is missing, the rate limit is exceeded, or
            the request fails.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds value by detailing return content, error conditions (ToolError for missing key, rate limit, request failure), and output formats. It is fully transparent and consistent with annotations.

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?

The description is well-structured with clear sections and front-loaded purpose. Every sentence adds value, there is no fluff, and it is appropriately sized for the tool's complexity.

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

Completeness5/5

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

Given the tool has one parameter (nested object), comprehensive annotations, and an output schema, the description is complete. It covers usage context, return values, and error handling, leaving no gaps.

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 input schema provides detailed descriptions for all parameters, so baseline is 3. The description lists the parameter groups but adds minimal extra meaning beyond what the schema already offers.

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 the tool retrieves parsed Google Jobs listings for a query. It specifies the verb (Retrieve) and resource (parsed Google Jobs listings). It distinguishes from siblings like google_search and google_news by explicitly stating when NOT to use this tool and suggesting alternatives.

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

Usage Guidelines5/5

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

The description has explicit 'When to use' and 'When NOT to use' sections, providing clear context for usage. It guides the agent to use this tool for job aggregations and labor-market research, and to avoid it for general web results, directing to alternative tools.

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/scraperapi/scraperapi-mcp'

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