Skip to main content
Glama
Jobs Every Hour MCP server

Jobs Every Hour MCP server

Jobs by category

jobs_by_category

Find open jobs in a specific field of work, such as engineering, design, sales, or healthcare. Filter by remote-only and limit results to the newest listings.

Instructions

Open jobs in a field of work, such as engineering, design, sales, marketing, healthcare or operations.

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": {
      "category": "<category>"
    },
    "name": "jobs_by_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many of the newest jobs to show, 1 to 30
categoryYesA field of work, e.g. engineering
remote_onlyNoOnly remote jobs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose that results are limited to 'open' jobs (implying closed/expired postings are excluded), which is genuinely useful. However, it says nothing about ordering, pagination, result volume beyond the schema's limit, or whether the call is a safe read — for a zero-annotation tool this leaves significant gaps.

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?

A single front-loaded sentence that defines the resource and immediately grounds it with examples. No filler, no redundancy, and the key qualifier ('Open jobs') appears first.

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 simple three-parameter, fully schema-documented tool with no output schema, the description gives enough to call it correctly: what is returned (open jobs) and valid category examples. The remaining gap is routing guidance against the sibling job-listing tools, which is not addressed.

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 adds value beyond the schema by supplying concrete example category values (engineering, design, sales, marketing, healthcare, operations) where the schema only says 'A field of work, e.g. engineering'. It does not discuss limit or remote_only, but those are well documented in the schema.

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 concrete resource and scope: open jobs filtered to a field of work, with illustrative categories (engineering, design, sales, marketing, healthcare, operations). An agent can tell this is a category-filtered job listing rather than a company, location, or skill lookup. It stops short of explicitly naming a sibling, so a 4 rather than a 5.

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 implied by the phrase 'Open jobs in a field of work' — call it when you want jobs grouped by a category such as engineering. There is no explicit when-to-use versus jobs_by_company, jobs_by_location, jobs_by_skill, or latest_jobs, and no statement of when not to use it. The agent must infer the routing from the tool name and the single category parameter.

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