Skip to main content
Glama

BirJob

Save a job search

create_job_alert

Save a search (the same filters as search_jobs) to check later with get_new_matches. Use this when the user wants to follow a search over time. Each call saves another search. Nothing is emailed or sent on a schedule: new jobs are found only when get_new_matches is called. Do not use for a one-off search (search_jobs). 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": "create_job_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoA city or district of Azerbaijan, as for search_jobs.
nameNoA short name for the saved search, e.g. "Python in Baku". Made from the filters if left out.
queryNoWords in the job title or company name, as for search_jobs.
remoteNoWork format, as for search_jobs (default exclude).
countryNoAZ (default), UZ, KZ, TR, GE or KG.
categoryNoA field of work, as for search_jobs.
salary_minNoLowest monthly pay in manat (AZN). Azerbaijan only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that each call saves another search (non-idempotent accumulation, consistent with idempotentHint=false), that nothing is emailed or scheduled, and that matches surface only when get_new_matches is called. It also discloses the auth prerequisite (signed-in BirJob job seeker account with an interactive sign-in/consent on first call), which annotations cannot express.

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?

Four short sentences, front-loaded with what it does and the follow-up tool, then usage, then the critical non-obvious behavior (no emailing/scheduling), then exclusions and auth. No redundant restatement of the title or schema.

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?

For a no-required-param mutation tool with full schema coverage and no output schema, the description covers persistence behavior, the retrieval dependency, the sibling alternative, and the interactive auth flow. Nothing an agent needs in order to call it correctly and set user expectations is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description adds value by tying every filter to search_jobs semantics and by noting that `name` is auto-derived from the filters when omitted. It stops short of explaining the remote enum values or salary_min's AZN/Azerbaijan-only constraints in the description body, leaving those to the schema.

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+resource ("Save a search") and scopes it by pointing at the same filters as search_jobs. It explicitly distinguishes itself from search_jobs (one-off) and get_new_matches (the retrieval counterpart), so an agent can pick it 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 explicit when-to-use ("when the user wants to follow a search over time") and when-not-to-use ("Do not use for a one-off search (search_jobs)"), naming the alternative tool. It also clarifies the follow-up path via get_new_matches.

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