Skip to main content
Glama

List saved job listings

listSavedJobs
Read-onlyIdempotent

List the job board listings saved so far, newest first.

Listings that have closed since they were saved are still here, with isLive false — they are kept on purpose rather than disappearing. Point them out and offer to search for something close instead.

applyToJob with a row's jobId applies for them.

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
jobsYes
hasMoreYes
nextCursorYes
closedCountYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, and the description adds non-obvious behavior beyond them: closed listings persist with isLive false by design rather than disappearing, and the tool's inputs and results are recorded for usage tracking and support. Only the pagination behavior is left to the schema.

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?

Front-loaded with purpose and ordering, then behavior, then a cross-tool pointer, then the data-handling note. Sentences each carry distinct information; the closing telemetry sentence is unusual but purposeful rather than filler.

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?

An output schema exists, so return shapes need not be enumerated, and the description still explains the one field an agent must interpret (isLive). The remaining gap is parameter coverage — perPage is undocumented in both places.

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

Parameters2/5

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

Schema description coverage is only 50% — cursor is documented in the schema, but perPage carries no description and the tool description never mentions page size or its 1–50 bounds. Since coverage is low, the description should have compensated and does not.

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?

States a specific verb and resource ("List the job board listings saved so far") plus the ordering ("newest first"), which is enough to separate it from passJob/listPassedJobs-style siblings and from searchJobs. No ambiguity about what comes back.

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?

Gives actionable follow-up guidance — flag closed listings and offer an alternative search — and routes the agent to applyToJob with a row's jobId for the next step. It does not state explicit exclusions against siblings like listPassedJobs or searchJobs, so it falls short of a full when/when-not rubric, but the usage context is clear.

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