Skip to main content
Glama

BirJob

Remove a saved BirJob job

unsave_job
DestructiveIdempotent

Remove a job from the user's BirJob saved jobs. Use this only when the user asks to remove or unsave a job. Cannot be undone from here; the job can be saved again with save_job. 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": "unsave_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.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the bar is lower, and the description still adds real value: it discloses that the action cannot be undone from here, that save_job restores it, and that the first call triggers a BirJob sign-in and consent flow. What is missing is failure behavior in prose (e.g., what happens when the job was never saved), though idempotentHint partially covers that.

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?

Three short sentences, zero padding, with the action and its scope front-loaded before the usage restriction, reversibility note, and auth requirement. Every sentence carries information the agent needs.

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 single-parameter destructive tool with full annotation coverage and no output schema, the description covers the remaining gaps an agent would care about: trigger condition, irreversibility, recovery path, and the sign-in prerequisite. Nothing needed to call it correctly is absent.

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?

There is a single parameter at 100% schema description coverage, and the schema already explains that job_id accepts either an id from search_jobs or a birjob.com job URL. The description adds no parameter-level meaning beyond that, so the baseline of 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?

"Remove a job from the user's BirJob saved jobs" gives a specific verb (remove) and a precisely scoped resource (the user's saved jobs list). It is immediately distinguishable from save_job and get_saved_jobs 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states an explicit trigger condition with a restrictive qualifier: "Use this only when the user asks to remove or unsave a job." It also names save_job as the recovery path, which implicitly frames the alternative. It stops short of naming the read-side sibling (get_saved_jobs) or stating a when-not-to-use case beyond the positive condition, so it falls one step below the top score.

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