Skip to main content
Glama

L50 Job Search

jobs search

jobs_search
Read-only

Live job listings from Indeed and Glassdoor (plus Google Jobs, ZipRecruiter) in 30 countries for a job title and location: up to 50 jobs with company, salary, job type, remote flag, date posted and links, plus a summary (salary range per year, top employers, remote share). Costs $0.10 per call, paid in USDC on Base with x402.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "jobs_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesJob title or keywords, e.g. electrician
maxNoJobs to return (default 25)
sitesNoComma list of indeed, glassdoor, google, zip_recruiter (default indeed,glassdoor)
remoteNoRemote jobs only
countryNoCountry (default uk), e.g. usa, germany
jobTypeNoJob type
locationNoTown, city or region, e.g. Manchester
descriptionsNoInclude full job descriptions (default false)
postedWithinHoursNoOnly jobs posted in the last N hours

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description is consistent with them. It adds materially useful behavior beyond them: a $0.10 per-call cost paid in USDC on Base via x402 (an agent must know payment is required) and the exact shape of returned job records plus an aggregate summary. It stops short of rate limits, pagination, or failure/refund behavior for a paid call.

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?

Two sentences, front-loaded with the resource and source coverage before the return fields and pricing. Dense but each clause carries information; the long first sentence is a minor readability cost rather than filler.

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?

Nine parameters, all schema-described, and no output schema — so the description's enumeration of returned fields and summary contents is important and well handled, as is the payment model. Minor gaps remain around pagination and what happens on a failed or unpaid call.

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 description coverage is 100%, so the baseline is 3. The description reinforces the two primary inputs (job title, location) and the 50-job ceiling, but adds no syntax, format, or interaction detail beyond what the schema already documents.

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 and resource (live job listings search) and enumerates the sources (Indeed, Glassdoor, Google Jobs, ZipRecruiter), country coverage, and per-call result cap. An agent knows exactly what this tool returns without opening the schema.

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

Usage Guidelines3/5

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

Usage is implied by the framing ('for a job title and location'), and the default site/country behavior is discoverable, but there is no explicit when-to-use versus when-not guidance. With no siblings the routing burden is low, so implication is tolerable rather than disqualifying.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources