Skip to main content
Glama

List passed job listings

listPassedJobs
Read-onlyIdempotent

List the job board listings the candidate hid with passJob, newest first. Position and company are null once a listing has left the feed. unpassJob with a row's jobId brings it back into searchJobs.

Clera privately records this tool's inputs and results for usage tracking and support.

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

Input Schema

NameRequiredDescriptionDefault
cursorNoPass nextCursor from a previous call to get the next page.

Output Schema

NameRequiredDescriptionDefault
jobsYes
hasMoreYes
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

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

With readOnly/idempotent/non-destructive annotations already supplied, the description still adds real behavior: results are ordered newest first, position and company become null once a listing leaves the feed, and the restore route is unpassJob. The privacy note about recording inputs and results is a further disclosure an agent would not otherwise know.

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?

The core behavior is front-loaded in the first sentence, and the nulling/restore details follow logically with no redundancy. The trailing data-recording sentence is boilerplate-adjacent and slightly dilutes the focus, though it is not wasted.

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 one-parameter, read-only list tool with an output schema and full annotation coverage, the description covers ordering, null-field behavior, and the restore path. Paging semantics are delegated to the schema, which is acceptable, leaving only minor gaps.

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?

There is a single cursor parameter with 100% schema description coverage, so the schema already explains paging. The description adds only the 'newest first' ordering that gives that cursor meaning, but nothing about page size or end-of-list signaling.

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 first sentence names a specific verb and resource ('List the job board listings') and narrows the set to those the candidate hid with passJob, plus an ordering guarantee. It explicitly distinguishes this listing from the feed via searchJobs and from the reverse action via unpassJob, so an agent can identify it without opening the schema.

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

Usage Guidelines4/5

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

It states the retrieval condition (listings hidden via passJob) and names the follow-up path (unpassJob with a row's jobId) and the alternative view (searchJobs), which is clear context. It stops short of explicit when-not-to-use guidance, e.g. how it differs from the sibling listPassed.

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