Skip to main content
Glama

BirJob

New BirJob jobs since a time

new_since
Read-only

Jobs BirJob first listed after a given time that match the same filters as search_jobs, newest first, with the same fields. Use this when the user asks what is new since a date or since the last check: keep the time of each call and pass it as since next time. since may be up to 30 days back. Do not use for a general search (search_jobs with posted_within_days covers "this week").

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": {
      "since": "<since>"
    },
    "name": "new_since"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoA city or district of Azerbaijan, in Azerbaijani, English or Russian spelling: "Bakı" / "Baku" / "Баку", "Gəncə" / "Ganja" / "Гянджа", "Sumqayıt" / "Sumgait" / "Сумгаит", "Şəki" / "Shaki" / "Шеки". Leave out for the whole country.
pageNoResult page, 1 to 20 (default 1), 10 results a page. Past page 20, send the user to search_url.
queryNoWhat the user is looking for, in their words: a job title, skills or a sentence about their work ("python", "mühasib", "accountant", "I build production LLM systems with Python and Azure"). Matched by meaning in the title, company and description, across Azerbaijani, English and Russian (mühasib = accountant = бухгалтер; LLM finds AI and ML roles); jobs whose title fits best come first. Azerbaijani letters are optional. Put the place, country, category, company, work format, job type, seniority and pay in their own fields. Leave out to browse.
sinceYesISO 8601 date or time, within the last 30 days: "2026-11-20" or "2026-11-20T08:00:00Z". Returns jobs BirJob first listed after it. Keep the time of your last call and pass it next time.
remoteNoWork format. exclude (the default, as on birjob.com): every job except remote ones. only: remote jobs only. any: every job. onsite or hybrid: jobs that say so. Always within the chosen country.
companyNoOne employer's jobs: its birjob.com company page URL or slug (from list_companies or a job's company_url), or its name.
countryNoWhich board to search: AZ (Azerbaijan, the default), UZ (Uzbekistan), KZ (Kazakhstan), TR (Turkey), GE (Georgia) or KG (Kyrgyzstan). city applies to AZ only.
categoryNoA field of work: it (IT / Texnologiya), proqram-tertibati (Proqram Tərtibatı), data-analitika (Data və Analitika), maliyye (Maliyyə / Mühasibat), satis (Satış / Marketing), huquq (Hüquq), muhendislik (Mühəndislik), bank (Bank / Sığorta), insan-resurslari (İnsan Resursları), tibb (Tibb / Səhiyyə), aqro-kend-teserrufat (Aqro / Kənd Təsərrüfatı), neft-qaz (Neft-Qaz), suni-intellekt (Süni İntellekt / AI).
page_sizeNoResults a page, 1 to 25 (default 10). Keep the same page_size while paging.
seniorityNoKeep only jobs whose stated career level is one of these: intern (təcrübəçi, стажёр), junior (kiçik mütəxəssis, младший), mid (orta, средний), senior (böyük mütəxəssis, старший), lead (rəhbər, ведущий), exec (top menecer, руководитель). Most postings state none, so this narrows a lot.
salary_minNoLowest monthly pay. Keeps only jobs that state a salary at least this high, in salary_currency (default AZN on the Azerbaijan board). Nothing is converted between currencies.
work_formatNoremote (uzaqdan, удалённо), hybrid (hibrid, гибрид) or onsite (ofisdə, в офисе): the same as remote=only, hybrid or onsite. Send this or remote, not both.
employment_typeNoKeep only jobs that state one of these types: full_time (tam ştat, полная занятость), part_time (yarım ştat, частичная занятость), contract (müqavilə, контракт), internship (təcrübə, стажировка), temporary (müvəqqəti, временная). A job that states no type is left out.
salary_currencyNoISO currency of salary_min. Alone, keeps only jobs that state pay in this currency. Required for salary_min outside Azerbaijan.
exclude_employment_typeNoLeave out jobs that state one of these types, e.g. ["internship"]. A job that states no type stays.

Output Schema

NameRequiredDescriptionDefault
jobsYes
pageYes
notesYes
pagesYesPages an assistant can read, at most 20.
totalYesOpen jobs that match.
filtersYes
next_pageYes
page_sizeYes
search_urlYesThe same search on birjob.com, with every result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false and idempotentHint=false; the description adds real context beyond that: results are newest-first, they carry the same fields as search_jobs, and the window is capped at 30 days. The recommended stateful "store the call time, pass it next time" loop is the kind of usage behavior an agent cannot derive from annotations alone. It does not discuss pagination behavior or what happens at the 30-day boundary, which keeps it off a 5.

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 sentences, front-loaded with the purpose, then the usage pattern, then the limit, then the anti-pattern. Every clause carries information an agent needs; nothing is repeated from the schema or the title.

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?

With 15 parameters, full schema coverage, five enums, an output schema, and rich annotations, the remaining burden on the description is behavioral and routing guidance — both are covered. An agent can decide between this and search_jobs and invoke it correctly from this text alone.

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 description coverage is 100%, so the baseline is 3, and the description earns above that by declaring that the 14 filter parameters reuse search_jobs semantics ("match the same filters as search_jobs"), which lets an agent transfer known parameter behavior across tools. The 30-day constraint on `since` is restated rather than newly explained, so the addition is narrow but genuine.

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?

"Jobs BirJob first listed after a given time that match the same filters as search_jobs, newest first, with the same fields" gives a specific resource (jobs), a specific selection criterion (first listed after `since`), and an ordering guarantee. It is immediately distinguishable from search_jobs and get_new_matches 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 states the triggering user intent ("what is new since a date or since the last check"), the operational pattern ("keep the time of each call and pass it as since next time"), a hard limit ("since may be up to 30 days back"), and an explicit exclusion with the correct alternative ("Do not use for a general search (search_jobs with posted_within_days covers 'this week')"). When-to-use, when-not-to-use, and the substitute are all present.

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