Skip to main content
Glama

BirJob

New jobs for a saved search

get_new_matches

The jobs that reached BirJob since this saved search was last checked and match it, newest first, up to 10, each with its birjob.com URL. Marks the search as checked now. Use this when the user asks what is new for a search they saved. Do not use for a search that is not saved (new_since). 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

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": {
      "alert_id": "<alert_id>"
    },
    "name": "get_new_matches"
  }
}

Input Schema

NameRequiredDescriptionDefault
alert_idYesThe id from create_job_alert or get_job_alerts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the side effect that the search is marked as checked now — which is exactly what makes readOnlyHint=false and idempotentHint=false true — plus the 10-result cap, sort order, returned URL, and the first-call sign-in/consent flow. The only real gap is behavior on an invalid or foreign alert_id, which is not covered.

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?

Four tight sentences, front-loaded with what the tool returns before moving to usage and prerequisites. No filler, though the auth sentence could be folded in slightly more compactly.

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, but the description compensates by describing the result shape (up to 10 items, newest first, each with its URL) and the mutation side effect. For a single-parameter tool with full schema coverage, nothing an agent needs to call it correctly is missing.

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% and the alert_id description already names its sources (create_job_alert or get_job_alerts). The prose calls it a 'saved search' but adds no new detail about format or validation beyond the schema, so the baseline of 3 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?

States a specific resource and scope: jobs that arrived since the saved search was last checked and match it, ordered newest first, capped at 10, each with its URL. It explicitly distinguishes itself from the similarly named sibling new_since, so an agent can choose 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?

Gives an explicit positive trigger ('when the user asks what is new for a search they saved') and an explicit exclusion with the alternative ('Do not use for a search that is not saved (new_since)'). It also states the account prerequisite, so the agent knows the call may surface a sign-in prompt.

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