Skip to main content
Glama
Jobs Every Hour MCP server

Jobs Every Hour MCP server

What can be searched

list_feeds

List skills, categories, locations, or companies that have a job feed with open job counts, and optionally filter by name to find relevant feeds.

Instructions

The skills, categories, locations or companies that have a feed, with the number of open jobs in each.

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": {
      "kind": "<kind>"
    },
    "name": "list_feeds"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
containsNoOnly names containing this text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It hints at the return shape (each feed value paired with a count of open jobs) but says nothing about whether this is read-only, how results are ordered or capped, whether feeds without jobs appear, or what permissions are required.

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 tight sentence with no filler, and the returned resource is front-loaded before the detail about job counts. Nothing is wasted, though the sentence could have led with a verb to make the action explicit.

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 simple two-parameter discovery tool with no output schema, it covers what is returned and enough to call it correctly. Gaps remain on ordering, whether zero-job feeds are included, and pagination of the returned list, which an agent would need to know before relying on the output.

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 50%: `contains` is already documented in the schema ('Only names containing this text') and `kind` has a self-documenting enum. The description's enumeration of the four kinds merely restates the enum, and it adds no meaning for `contains` (matching rules, case sensitivity) beyond the schema text.

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 the resource ('the skills, categories, locations or companies that have a feed') and states what accompanies each entry ('the number of open jobs in each'). That distinguishes it from the jobs_by_* siblings, which return jobs rather than the list of filterable values. It lacks an explicit verb like 'List', relying on a noun phrase plus the title 'What can be searched'.

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 discovery step before calling jobs_by_category/jobs_by_company/etc., but the description never says so or names those alternatives. There is no explicit when-to-use or when-not-to-use statement, and no note that this returns the allowed filter values rather than job records.

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