Skip to main content
Glama

Search Job Postings

search_job_postings
Read-onlyIdempotent

Search US job postings by active timeframe or date range, title, and city using metadata-discovered filters; returns paginated posting data for job market analysis.

Instructions

Search US postings with native filters including required when (active or a start/end range), e.g. {"when": "active", "title": ["ET6850661D6AE5FA86"], "city_name": ["Seattle, WA"]}. Use metadata to discover filters; requires postings:us.

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": {
      "filters": "<filters>"
    },
    "name": "search_job_postings"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo
fieldsNo
filtersYesA required timeframe plus native JPA filter fields discovered in metadata.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/open-world, so safety is covered. The description adds genuinely non-redundant behavior: a required permission scope (`postings:us`), a US-only coverage boundary, and the fact that the filter surface is open-ended and must be discovered from metadata.

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?

Purpose, filter requirement, worked example, discovery hint, and permission scope are packed into roughly two sentences with no filler, and the core purpose is front-loaded.

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?

An output schema exists, so return values need not be explained, and the free-form filter model is conveyed. But pagination behavior and the `fields` projection parameter are undocumented, which matters for a search tool capped at 10 results per page.

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 low (25%), so the description must carry weight. It does explain the required `when` semantics ("active" or a start/end range) and shows that arbitrary filter keys like `title` and `city_name` are permitted via a concrete example. It says nothing about `page`, `limit` (max 10), or `fields`, leaving a third of the parameters unexplained in both schema and prose.

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?

The description states a specific verb and resource ("Search US postings") plus the defining constraint that filters are native JPA fields with a required `when`. It clearly scopes to US postings, but does not name any sibling (e.g., search_job_titles) to contrast itself against.

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?

It gives a prerequisite ("requires postings:us") and a procedural hint ("Use metadata to discover filters") that points an agent at the metadata endpoint before calling. However, it never says when to choose this over sibling search tools or when not to use it.

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