Skip to main content
Glama
Jobs Every Hour MCP server

Jobs Every Hour MCP server

Jobs by location

jobs_by_location

Search current open jobs by country, region, city, or remote, with a configurable limit and an option to show only remote roles.

Instructions

Open jobs in a country, region or large city, such as united-states, europe, london, new-york or remote.

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": {
      "location": "<location>"
    },
    "name": "jobs_by_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many of the newest jobs to show, 1 to 30
locationYesA country, region or city, e.g. Germany
remote_onlyNoOnly remote jobs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It conveys the domain and gives concrete location values, and the tool is evidently a low-risk read, but it says nothing about result ordering or how location matching works (exact slug vs. fuzzy city/region containment) — the ordering hint 'newest jobs' lives only in the schema's limit parameter.

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 with no filler, and the examples are the most information-dense part. The trailing 'or remote' as a location value slightly muddies things by overlapping with the separate remote_only boolean parameter, costing it the top score.

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 three-parameter read tool with complete schema descriptions and no output schema, this is adequate but thin. It never indicates what a returned job contains, how many fields, or whether location matches broaden to a region containing the city, which an agent would need to set expectations without an output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns above baseline by demonstrating the location value format with hyphenated lowercase slugs ('united-states', 'new-york', 'europe'). That is genuinely useful because the schema's own example ('Germany') shows a different casing style, so the description helps disambiguate the expected input.

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 verb and resource ('Open jobs') and constrains the scope to a location dimension (country, region, large city), which separates it from jobs_by_category, jobs_by_company and jobs_by_skill by implication. It does not explicitly name a sibling as the alternative, but the resource scope is unambiguous.

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: the location-scoped framing tells an agent this is the tool when the filter is geographic, but there is no explicit when-to-use statement, no exclusion, and no guidance on how it relates to latest_jobs (which appears to return the same set unfiltered). Nothing is misleading, but the agent must infer the routing.

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