Skip to main content
Glama

BirJob

Track a job application

track_application
Idempotent

Record where the user is with a job on BirJob: saved, applied, interview, offer, rejected. Use this when the user says they applied, got an interview, an offer or a rejection. Calling it again for the same job changes the status. Do not use to apply: it records the status for the user only, and does not apply to the job or contact the employer. 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>",
      "status": "<status>"
    },
    "name": "track_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe job id from search_jobs, or its birjob.com job URL.
statusYessaved (interested), applied, interview, offer or rejected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the authentication flow (signed-in BirJob job seeker account, first call triggers a sign-in/permission prompt) and confirming the call has no external effect on the employer. Re-invocation semantics ('Calling it again for the same job changes the status') clarify mutation behavior in a way the idempotentHint flag alone does not, and nothing conflicts with readOnlyHint=false or destructiveHint=false.

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 distinct information: the state model first, then the trigger, then repeat-call behavior, then the exclusion and auth requirement. No filler or repetition.

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 two-parameter status-setting tool with no output schema, the definition covers purpose, trigger, repeat behavior, scope limit, and the sign-in prerequisite an agent must be ready to relay. Nothing needed to call it correctly is missing, and return values are unnecessary to describe for a status write.

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%, with job_id already documented as a search_jobs id or birjob.com URL and status carrying its own enum descriptions. The description restates the same five status values but adds no new syntax, format, or sourcing detail, so the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (record the user's stage for a job on BirJob) and enumerates the exact status domain, so the operation is unmistakable. It does not differentiate against the closely related save_job sibling, which also covers a 'saved' state, leaving a small ambiguity an agent must resolve on its own.

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?

Gives concrete trigger language ('when the user says they applied, got an interview, an offer or a rejection'), states the repeat-call behavior, and adds an explicit exclusion ('Do not use to apply: it records the status for the user only, and does not apply to the job or contact the employer'). That is a clear when/when-not pair.

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