Skip to main content
Glama

BirJob

Match BirJob jobs to a CV

match_jobs
Read-onlyIdempotent

Rank open jobs in Azerbaijan on BirJob against a role, skills or CV text, with the words each job matched and why. Use this when the user shares a CV or a list of skills and asks which jobs fit. Pass title, skills and/or cv_text: they are used for this one call and not stored. No sign-in needed. Or set use_profile to true to use the signed-in user's own BirJob CV profile (title, skills, experience); that asks the user to sign in to BirJob. Do not use for a plain search by job title (search_jobs).

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

Input Schema

NameRequiredDescriptionDefault
titleNoThe role the user wants, e.g. "Baş mühasib", "Frontend Developer".
skillsNoSkills, comma-separated: "Python, SQL, Excel".
cv_textNoThe CV's text, up to 20000 characters. Used for this call only, never stored. Leave out contact details.
use_profileNotrue: use the signed-in user's BirJob CV profile instead of the text passed. Needs sign-in.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses that the passed text is used for this call only and never stored, that the text path needs no sign-in, and that use_profile requires signing in to BirJob. That is meaningful auth and data-handling context the annotations cannot convey. It stops short of anything on rate limits or result size, so a 4 rather than 5.

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?

Front-loaded with the core action and result shape, then usage, privacy, profile branch, and the exclusion, in a logical order. The only waste is the mild duplication of the schema's "Used for this call only, never stored" wording on cv_text, which is repeated in prose.

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 compensates by explaining what comes back (matched words and rationale per job). Given four optional parameters, it also clarifies that at least one of title/skills/cv_text is expected and how the profile path differs, which is everything needed to call it correctly.

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 documents each field and its limits, making 3 the baseline. The description still adds real meaning: title/skills/cv_text can be combined ("and/or") and are session-only, while use_profile switches the entire source of truth to the user's stored BirJob CV profile rather than supplementing 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 gives a specific verb and resource ("Rank open jobs in Azerbaijan on BirJob"), the inputs it ranks against (role, skills, CV text), and the shape of the answer ("the words each job matched and why"). It also explicitly contrasts itself with search_jobs by job title, so an agent can separate the two 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 trigger condition ("when the user shares a CV or a list of skills and asks which jobs fit") and the negative case ("Do not use for a plain search by job title (search_jobs)"), naming the alternative. It also spells out the profile-based branch and its sign-in prerequisite, 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