Skip to main content
Glama

Browse job results

browse_jobs
Read-onlyIdempotent

The job widget's paged search. Same filters as search_jobs; level takes a comma-separated list.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browse_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page of 40 postings.
sortNonewest or salary.
levelNo
queryNo
regionNo
countriesNo
workplaceNo
jobFunctionNo
postedWithinNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description adds little beyond 'paged' (already implied by the page parameter) and says nothing about ordering guarantees, result caps, or how paging interacts with sort. For a read-only tool with rich annotations this is acceptable but thin.

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?

Two short sentences, zero filler, with the identity of the tool and the one non-obvious parameter rule front-loaded. Nothing could be removed without losing information.

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 nine-parameter, read-only browse tool with no output schema, the description covers paging and one filter format but leaves most filter semantics to a cross-reference. An agent can call it correctly enough, yet may still need to inspect search_jobs to use the filters well.

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 only 22%, with seven of nine parameters undocumented there, so the description carries real weight. It does add a genuine clarification the schema lacks — 'level takes a comma-separated list' — and delegates the remaining filter formats to search_jobs, but query/region/countries/workplace/jobFunction/postedWithin formats remain unstated.

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 the verb and resource plainly: a paged search over job postings, and implicitly contrasts it with search_jobs by emphasizing paging. The phrase 'the job widget's paged search' is a bit insider-ish and never explicitly says it returns job listings, but an agent can still distinguish it from search_jobs and get_job.

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?

'Same filters as search_jobs' implies this is the paginated variant to use when iterating results, which is usable guidance. However it never states when to prefer this over search_jobs, nor when get_job is the right alternative, so the choice is left to 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.