Skip to main content
Glama

BirJob

List saved BirJob jobs

get_saved_jobs
Read-onlyIdempotent

List the user's saved jobs on BirJob, newest first, with each job's birjob.com URL; a job no longer open is marked closed. Use this when the user asks what they saved. Do not use for applications (get_applications). Needs a signed-in BirJob job seeker account: the first call asks the user to sign in to BirJob and allow access.

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

Input Schema

NameRequiredDescriptionDefault
pageNoResult page, 1 to 100 (default 1), 10 a page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds context annotations cannot express: results are newest-first, closed jobs are flagged rather than dropped, and the first call triggers a sign-in/consent flow with BirJob. That auth prerequisite is the kind of behavioral fact an agent needs before calling.

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?

Three sentences, no filler, and the structure is front-loaded: what it returns first, then when to use it, then the exclusion and prerequisite. Every sentence carries distinct information.

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?

There is no output schema, so the description carries the return-value burden and does so by describing ordering, URL inclusion, and closed-job marking. Combined with the disclosed auth prerequisite and the schema-documented pagination, an agent has everything needed to call and interpret this tool.

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 coverage is 100%: the single 'page' parameter is fully documented in the schema, including its 1-100 range and 10-per-page sizing. The description adds no additional meaning about paging or how to iterate pages, so the baseline 3 for a schema-complete tool applies.

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 names a specific verb and resource (list the user's saved jobs on BirJob) and adds what the results contain: newest-first ordering, each job's birjob.com URL, and a closed marker for jobs no longer open. It also distinguishes itself from get_applications by name, so an agent can route between them without opening either schema.

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 gives an explicit positive trigger ('Use this when the user asks what they saved') and an explicit exclusion with the alternative ('Do not use for applications (get_applications)'). This is a clear when/when-not pair with a named sibling, leaving nothing to inference.

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