Skip to main content
Glama

SourceGeek

Search jobs

employee_search_jobs_v2
Read-only

Search live job postings by keywords with an optional geo id, a distance radius (0, 5, 10, 25, 50 or 100 miles), company ids, date-posted, job type, experience level, onsite/remote, salary and sort filters. Returns job id, title, url, company, location, posted date and benefits when listed.

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": {
      "keywords": "<keywords>"
    },
    "name": "employee_search_jobs_v2"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo
limitNoMaximum items to return (1-100, default 10). Results beyond the provider's page are not fetched.
startNoOffset in steps of 25 (0, 25, 50 … max 975).
salaryNoMinimum yearly salary bucket.
jobTypeNo
distanceNoRadius in miles around locationId.
keywordsYesJob title or keywords, e.g. 'senior data engineer'.
titleIdsNoTitle ids (only if known).
companyIdsNoNumeric company ids.
datePostedNo
locationIdNoGeo id.
functionIdsNoJob-function ids (only if known).
industryIdsNoIndustry ids (only if known).
onsiteRemoteNo
experienceLevelNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds genuine value by naming the returned fields (job id, title, url, company, location, posted date, benefits) in the absence of an output schema. It says nothing about rate limits, result caps beyond the schema's own note, or provider coverage, so it does not go far beyond the annotations.

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?

Front-loaded with the core action and scope, then a single dense clause for filters and one for return values. The long filter enumeration is efficient if slightly list-like, and no sentence is wasted on filler.

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 15-parameter tool with no output schema, the description does cover the return shape and the main filter axis, which is the minimum an agent needs. It leaves out pagination semantics (limit/start interaction), any routing guidance among the job-search siblings, and the meaning of 'live' versus archived postings.

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?

At 67% schema coverage the schema already documents most parameters, and the description mostly re-lists filters that are self-explanatory from their names. It restates the distance enum values verbatim (redundant with the schema) and omits any mention of limit, start, titleIds, functionIds and industryIds. The one useful clarification, that distance is a radius around a geo id, is also already in the schema.

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 and resource ('Search live job postings') and enumerates the filter surface, so the agent knows exactly what the tool does. It does not distinguish itself from the similarly named siblings (employee_search_jobs, fast_search_jobs, precision_search_jobs), leaving that discrimination to the agent.

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?

The description lists available filters but gives no guidance on when to prefer this tool over the several adjacent job-search siblings, nor any exclusions. The word 'live' hints that expired postings are excluded but is never stated as a selection criterion.

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