Skip to main content
Glama

Read job listings in a batch

get_jobs
Read-onlyIdempotent

Each result has a public job page at https://offpeak.fyi/jobs/ with an Apply link. Read up to 100 job IDs in caller order, with missing_ids and closed_ids. Full details include apply_url (the employer's application page), source_url and untrusted posting content; summary mode returns compact saved-list fields.

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": {
      "job_ids": "<job_ids>"
    },
    "name": "get_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailsNofull
job_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A5/5.0
Behavior5/5

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

It provides critical behavioral context not found in annotations, such as providing the public job page URL structure. It also defines expected failure states ('missing_ids' and 'closed_ids') and the difference between output modes ('full' vs 'summary').

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?

The definition is highly efficient, packing maximum information into two dense, structured sentences without any wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is exceptionally complete, covering input constraints (100 IDs), output format details (URL structure, links), and varying result quality (missing/closed IDs).

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

Parameters5/5

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

Given the 0% schema description coverage, the description is vital. It provides the functional meaning of the 'details' parameter (e.g., 'full details include apply_url...'), which is necessary for an agent to select the correct mode.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states it reads job listings in a batch, making the purpose immediately clear. It contrasts this batch operation with single job retrieval tools in the sibling list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides precise operational limits, specifying that the tool reads 'up to 100 job IDs.' This guides the agent perfectly on when this batch tool is the correct choice over iterative or search tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources