Skip to main content
Glama

SiteCheck Jobs & Property

Glassdoor job search: title, employer, employer rating

jobs_glassdoor_jobs
Read-only

Glassdoor job search: title, employer, employer rating, location, Glassdoor's estimated pay range (p10/p50/p90 with period and currency), age in days, easy-apply flag and link for up to 30 jobs, plus the total count. US-wide by keyword, or one city when you pass Glassdoor's city id (the IC number in a Glassdoor jobs URL, e.g. 1139761 = Austin, 1148170 = Denver). Via a residential proxy. Related tools on this server, for a different need: jobs_glassdoor when you need Glassdoor employer reviews: overall rating, review count. Price: $0.01 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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_glassdoor_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesJob keyword, e.g. 'python' or 'nurse'
limitNoHow many jobs, 1 to 30 (default 10)
cityIdNoOptional Glassdoor city id (digits after IC in a Glassdoor jobs URL), e.g. 1139761 for Austin, TX

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds material operational facts beyond them: access via a residential proxy, a $0.01 per successful call price paid through x402 across multiple networks, and that failed calls are not charged. It also discloses the 30-job ceiling and the city-id encoding convention (IC number in a Glassdoor URL, with worked examples).

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?

The purpose and returned fields are front-loaded, and the routing hint plus pricing follow logically. The prose is dense and somewhat run-on within the first sentence, but no sentence is redundant.

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?

For a three-parameter read-only search tool with an output schema present, the description covers everything needed to call it correctly: scope, geo mode, result cap, cost model, and the sibling to use for a different need. Return-value details are correctly left to the output schema.

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%, so all three parameters are already documented, including the cityId URL convention. The description reinforces the keyword/city scoping and the 30-job limit but introduces no syntax or constraints the schema does not already contain, so the 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 gives a specific verb and resource plus the exact returned fields (title, employer, rating, location, p10/p50/p90 pay range, age, easy-apply link) and caps scope at 30 jobs. It also explicitly distinguishes itself from the sibling jobs_glassdoor, which serves employer reviews rather than job listings.

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?

It states the two operating modes clearly: US-wide by keyword, or a single city when a Glassdoor city id is supplied. It also names the alternative and the condition that selects it ('jobs_glassdoor when you need Glassdoor employer reviews'), so the agent can route without inference.

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