Skip to main content
Glama
Jobs Every Hour MCP server

Jobs Every Hour MCP server

Newest jobs

latest_jobs

Retrieve recently posted open jobs from employers’ career pages, optionally limited to remote roles, with pay, posting date, and direct application links.

Instructions

The newest open jobs on Jobs Every Hour, read every hour from employers' own career pages (Greenhouse, Lever, Ashby, Workday, iCIMS and more).

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many of the newest jobs to show, 1 to 30
remote_onlyNoOnly remote jobs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose genuinely useful context not available elsewhere: sourcing from employers' own career pages across named ATS platforms and an hourly refresh cadence. It stops short of stating result ordering, pagination behavior, or what a returned record contains.

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?

A single front-loaded sentence that leads with the resource and then supplies provenance as supporting detail, with no filler. It is dense enough that nothing needs trimming, though it is arguably too terse to count as fully structured guidance.

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 two-parameter, zero-required read tool this is close to adequate: the agent knows what it gets and how fresh it is. The gap is that with no output schema, the description does not hint at the shape or ordering of results, leaving the agent to discover the return format by calling it.

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 100%, so both parameters (limit with its 1-30 bound, remote_only) are already fully documented and a baseline of 3 applies. The description adds no parameter-level detail beyond that, though "open jobs" reinforces the implicit filter on active postings.

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 names a specific resource ("the newest open jobs on Jobs Every Hour") and its provenance, which tells an agent exactly what kind of listing this returns. It never contrasts itself with the filter siblings (jobs_by_category, jobs_by_company, jobs_by_location), so sibling differentiation is left implicit.

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?

Usage is only implied: an agent can infer this is the unpivoted recency feed versus the by-category/company/location/skill tools. There is no explicit statement of when to prefer this over a filtered sibling, nor any stated exclusions or prerequisites.

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