Skip to main content
Glama

BirJob

Search jobs on BirJob

search_jobs
Read-onlyIdempotent

Search open job vacancies on BirJob (birjob.com), Azerbaijan's job board, which also lists Uzbekistan, Kazakhstan, Turkey, Georgia and Kyrgyzstan. Use this when the user asks for jobs or vacancies (vakansiya, iş, вакансии) by role, skill, place, employer, pay or date. Returns 10 jobs a page by default (page_size up to 25): title, company, place, work format, employment type, seniority, salary as numbers and currency, dates, a short snippet and each job's birjob.com URL. query is matched by meaning across Azerbaijani, English and Russian; put place, country, field, company, date, work format, job type, seniority and pay in their own fields. Do not use for one job's full text or apply link (get_job), or for jobs listed after a known time (new_since).

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

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.
sortNorelevance (the default with a query): best match first. newest (the default without a query): newest first. salary: highest stated monthly pay first (in manat, or in salary_currency when given), jobs without a salary last.
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.
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.
posted_within_daysNoOnly jobs posted in the last this many days, 1 to 30.
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.8/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds context annotations cannot: default page size of 10 with a 25 cap, semantic cross-language matching of query (mühasib = accountant = бухгалтер), Azerbaijani letters being optional, and that salary is returned as numbers plus currency with no conversion between currencies. These are real behavioral facts an agent needs to query and interpret results correctly.

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?

The structure is front-loaded and logical: purpose, when to use, what comes back, how query works, when not to use. The enumeration of returned fields (title, company, place, work format, ...) duplicates what the output schema and the page_size parameter already state, so that one clause is the only part that does not fully earn its place.

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 16-parameter, zero-required search tool with a full output schema and annotations, the description covers everything an agent needs: scope, defaults, paging limits, multilingual matching, and explicit exclusions. Nothing needed 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.

Parameters4/5

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

Schema coverage is 100%, so the schema already carries the per-parameter documentation and the baseline would be 3. The description goes beyond it by explaining how criteria should be distributed across fields ("put place, country, field, company, date, work format, job type, seniority and pay in their own fields") and by clarifying that query is meaning-matched rather than keyword-matched, which changes how an agent should phrase it.

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 opens with a specific verb and resource ("Search open job vacancies on BirJob") and names the covered country boards, so the scope is unambiguous. It explicitly distinguishes itself from get_job (single job full text/apply link) and new_since (jobs after a known time), so an agent can pick it over its siblings without opening any 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 when to use it ("user asks for jobs or vacancies (vakansiya, iş, вакансии) by role, skill, place, employer, pay or date") and when not to use it, naming the two sibling alternatives and the conditions that select them. It also gives routing guidance on what belongs in query versus the dedicated filter fields.

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