Skip to main content
Glama

Find jobs like a BirJob job

similar_jobs
Read-onlyIdempotent

Open jobs like one BirJob job (by its id from search_jobs, or its birjob.com URL): the same kind of role in other words and languages, in the same country, the same city first. Use this when the user likes a job and asks for more like it. 10 a page by default, with the same fields as search_jobs. Do not use for a new search by words or filters (search_jobs).

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

Input Schema

NameRequiredDescriptionDefault
idYesThe job id from search_jobs, or a birjob.com job URL (https://www.birjob.com/jobs/…).
pageNoResult page, 1 to 20 (default 1), 10 results a page. Past page 20, send the user to search_url.
page_sizeNoResults a page, 1 to 25 (default 10). Keep the same page_size while paging.

Output Schema

NameRequiredDescriptionDefault
jobYesThe job these are like.
jobsYes
pageYes
notesYes
pagesYes
totalYes
next_pageYes
page_sizeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the description's job is supplementary — which it does by disclosing the ranking behavior (city first, then country, cross-language/multi-lingual matching) and the default page size of 10. It stops short of describing failure modes (e.g. what happens when the seed job is expired or has no neighbors).

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 behavior and routing guidance, with zero filler sentences. The chain of qualifying clauses in the first sentence ('in other words and languages, in the same country, the same city first') is slightly dense but each clause carries real matching semantics.

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 an output schema present the description needn't enumerate return fields, and it still points to search_jobs for field parity. Combined with rich annotations and 100% schema coverage on three parameters, nothing an agent needs to invoke this correctly is missing.

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 description coverage is 100%, so the id/page/page_size semantics are already fully documented in the schema, including the URL form, the 1-20 page bound, the 1-25 page_size bound and the 'keep the same page_size while paging' caveat. The description adds only a mild reinforcement ('10 a page by default'), so baseline 3 applies.

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?

Names a specific verb and resource ('Open jobs like one BirJob job') and immediately defines what 'like' means: same kind of role in other words and languages, same country, same city first. It also distinguishes itself from the sibling search_jobs by naming it as the wrong tool for keyword/filter searches.

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?

Explicit when-to-use ('when the user likes a job and asks for more like it') and explicit when-not ('Do not use for a new search by words or filters (search_jobs)'), with the alternative named. An agent has no inference left to make about routing.

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