Skip to main content
Glama

BirJob

Read a BirJob job

get_job
Read-onlyIdempotent

Read one job on BirJob by its id (from search_jobs) or its birjob.com URL. Use this when the user wants the full description, requirements or how to apply for a job already found. Returns title, company, place, salary, work format, employment type, seniority, dates, the whole description and requirements as plain text (contact details removed), the apply link and its source. A closed job answers only its id, title, company and status closed. Do not use for searching: it reads one known job.

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": {
      "id": "<id>"
    },
    "name": "get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe job id from search_jobs, or a birjob.com job URL (https://www.birjob.com/jobs/…).

Output Schema

NameRequiredDescriptionDefault
jobYes
noteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description goes further by disclosing that contact details are stripped from the description and that a closed job returns only id, title, company and status. Those are non-obvious behavioral facts an agent cannot get from the annotations or schema.

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 tightly packed sentences, front-loaded with what the tool does before the usage clause, the return summary and the exclusion. Every sentence carries distinct information; nothing is redundant padding.

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?

Even though an output schema exists, the description summarizes the returned fields and flags the closed-job degradation, so an agent knows what to expect in both states. For a single-parameter read tool this leaves no meaningful gap.

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 single parameter already documents both the integer id from search_jobs and the birjob.com URL form, so the description adds no syntax or format detail beyond it. The only marginal value is reinforcing the search_jobs provenance, which the schema also states.

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 names a specific verb and resource ('Read one job on BirJob') plus the two accepted identifiers, and explicitly contrasts itself with searching ('it reads one known job'). An agent can distinguish it from search_jobs and similar_jobs 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 gives both the positive trigger ('when the user wants the full description, requirements or how to apply for a job already found') and an explicit exclusion ('Do not use for searching'), with the sibling search_jobs named as the id's source. Nothing about when to select this tool is left 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