Skip to main content
Glama

BirJob

Save a job on BirJob

save_job
Idempotent

Save a job to the user's BirJob saved jobs (the same list as on birjob.com). Use this when the user asks to save, bookmark or keep a job for later. Saving a saved job again changes nothing. Do not use to record an application (track_application). Needs a signed-in BirJob job seeker account: the first call asks the user to sign in to BirJob and allow access.

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": {
      "job_id": "<job_id>"
    },
    "name": "save_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe job id from search_jobs, or its birjob.com job URL.

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?

The annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description still adds genuinely new context the annotations do not carry: the authentication flow ("the first call asks the user to sign in to BirJob and allow access"). The idempotency sentence largely restates idempotentHint in user-facing terms, which is mildly redundant rather than contradictory.

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 short sentences, each carrying a distinct load: destination, trigger, idempotent behavior, exclusion, and auth prerequisite. The purpose and destination are front-loaded and nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter mutation tool with a rich annotation set, this covers the practical needs — what it does, when to call it, auth requirements, and safe re-calling. It does not indicate what a successful call returns (e.g. confirmation or the saved-job record), which is a small gap given no output schema exists.

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 schema's job_id description already explains "The job id from search_jobs, or its birjob.com job URL." The prose adds no syntax, format or edge-case detail beyond that, so the baseline 3 applies — the schema is doing the heavy lifting.

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 ("Save a job to the user's BirJob saved jobs") and anchors it to a concrete destination ("the same list as on birjob.com"). It explicitly separates itself from the nearest look-alike, track_application, so an agent can route without inspecting 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 intents ("save, bookmark or keep a job for later") and an explicit when-not-to-use with the named alternative: "Do not use to record an application (track_application)." That is the full when/when-not/alternative triad.

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