Skip to main content
Glama

PickedJobs

Get market statistics

get_market_stats
Read-onlyIdempotent

Statistics from open tech jobs on PickedJobs. Without filters: totals, posting recency, mix by category, specialty, seniority, work arrangement and employment type, hiring regions, top technologies, visa sponsorship and top sponsors, and disclosed USD yearly pay percentiles by seniority, specialty and work arrangement. With filters: the same breakdowns and listed USD yearly salary range for the matching jobs only. Does not use the job allowance.

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": "get_market_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoKeywords matched against job title, company and stack, e.g. "platform engineer".
roleNoOne or more engineering specialties. Implies category engineering.
stackNoOne or more technologies. Matches jobs mentioning any selected technology.
regionNoOne or more regions the candidate can work from.
remoteNoOne or more arrangements: remote, remote_region, hybrid or onsite.
companyNoCompany slug from a previous result's companySlug.
categoryNoKind of role.
salaryMinNoMinimum pay. Only matches jobs that publish salary. Defaults to USD per year.
seniorityNo
employmentNoOne or more employment types. eor: hired through an employer of record.
postedWithinNoOnly jobs posted in the last N days.
salaryPeriodNo
salaryCurrencyNoISO currency code for salaryMin, e.g. USD, EUR, GBP.
visaSponsorshipNoOnly jobs whose posting says the employer sponsors visas. Most postings don't say either way.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety needs no restating. The description adds genuinely non-structured behavior: the unfiltered call returns global aggregates while filtered calls return per-mode breakdowns plus a listed salary range for matching jobs only, and critically that the call consumes no job allowance. Remaining gaps (result size, aggregation semantics over array filters) are moderate against this solid baseline.

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 resource, then the unfiltered and filtered behaviors in order; three sentences with no filler. The long output enumeration is verbose but earns its place because there is no output schema. The trailing "Does not use the job allowance" is cryptic and would read better with context.

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?

For a 14-parameter, zero-required, read-only aggregate tool with no output schema, the description carries the return-value burden well by enumerating the metrics available in each mode. What is missing is how multiple filter values combine and whether results are bounded or sampled, which matters for a tool with 14 filter knobs.

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 86%, so the schema already documents nearly every parameter, including the implicit "role implies category engineering" note. The description adds only one semantic signal: filtered results differ in shape (listed USD yearly salary range) from unfiltered totals. It does not clarify multi-value filter combination logic (OR vs AND) or how seniority/salaryPeriod interact, so baseline 3 is right.

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?

"Statistics from open tech jobs on PickedJobs" gives a specific resource plus an exhaustive enumeration of what the statistics contain (recency, category/specialty/seniority mix, regions, top technologies, visa sponsorship, pay percentiles). An agent can tell this is an aggregate-report tool rather than a listing tool like search_jobs. It stops short of naming a sibling explicitly, so no credit for differentiation.

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?

The "Without filters / With filters" split implies when the two modes apply, and "Does not use the job allowance" hints at a quota-related reason to prefer this over a search call. But there is no explicit statement of when to use this versus search_jobs or get_new_jobs, and "job allowance" is never defined, so the routing guidance is implied rather than stated.

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