Skip to main content
Glama

Claim or skip a job

freeapply_claim_job

Claim a job before applying to run duplicate and rule checks, start tracking, and get the job_id needed for later updates. Use before an application form or to mark reviewed jobs skipped.

Instructions

Claims a job before you work on it: duplicate check, the user's rules, starts tracking, returns the job_id every later call needs. Makes the job's first record (listing: freeapply_list_jobs; changing: freeapply_update_job). Use: before opening any application form; also to record a reviewed job you won't pursue (status skipped + status_note) so it isn't reviewed again. Not for a job already claimed. Behavior, first match wins: posting id already tracked: returns that job (existing true, nothing added); job site the user didn't choose, or signed out or paused: refused (refused says why, sites lists ready ones); same company and title as an applied job: refused as a repost; posted pay below the user's minimum: saved as skipped (rule pay_floor). Otherwise the job is added. A refused or existing claim changes nothing, so repeating the call is safe. Returns: {job_id, existing, status, rule, earlier}. earlier: up to 20 other jobs at the company [{id, title, company, status, same_title}]; if an applied one is clearly the same role under another title, mark this one skipped (freeapply_update_job). restart true (auto-run): the user saved new settings and wants them used now: don't work this job; the run finishes and starts again. Errors: a missing title or company.

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": {
      "title": "<title>",
      "company": "<company>"
    },
    "name": "freeapply_claim_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPosting URL; tells the job site. The URL just read by freeapply_fetch_posting keeps its keywords.
titleYesAs posted.
sourceNoWhere found: job site id (linkedin, indeed, company_sites, ...) or referral; tells the job site like url.
statusNofound (default): to work on; skipped: a job you won't pursue.
companyYesThe employer as posted; not a staffing firm, when you can tell.
pay_maxNoHighest posted pay, a number. Feeds the pay floor.
pay_minNoLowest posted pay, a number: annual, or hourly if posted hourly. Feeds the pay floor.
locationNoAs posted.
pay_textNoPay exactly as posted, e.g. "$90k-$110k".
apply_urlNoApplication form URL, if different.
fit_notesNoWhy it fits or doesn't, one sentence.
fit_scoreNo0-100, scored as the apply procedure says.
work_modeNoremote, hybrid or onsite, as posted.
descriptionNoShort description or key requirements.
external_idNoThe posting's id on its source site; pass it whenever shown: finds the posting again and catches reposts.
status_noteNoFor skipped: why, one plain sentence.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv1.0.4
    • changedInput schema / properties / apply_url / description
      Previous value: -"Where the application form is, if different."New value: +"Application form URL, if different."
    • changedInput schema / properties / company / description
      Previous value: -"Employer name, as posted (not the staffing firm's name, if known)."New value: +"The employer as posted; not a staffing firm, when you can tell."
    • changedInput schema / properties / external_id / description
      Previous value: -"The posting's id on its source site; finds the same posting again, reposts included."New value: +"The posting's id on its source site; pass it whenever shown: finds the posting again and catches reposts."
    • changedInput schema / properties / fit_notes / description
      Previous value: -"Why it fits or doesn't, in one sentence."New value: +"Why it fits or doesn't, one sentence."
    • changedInput schema / properties / fit_score / description
      Previous value: -"Fit from 0 to 100, scored as the apply procedure describes."New value: +"0-100, scored as the apply procedure says."
    • changedInput schema / properties / location / description
      Previous value: -"Location as posted."New value: +"As posted."
    • changedInput schema / properties / pay_max / description
      Previous value: -"Highest posted pay as a number."New value: +"Highest posted pay, a number. Feeds the pay floor."
    • changedInput schema / properties / pay_min / description
      Previous value: -"Lowest posted pay as a number: annual, or hourly if posted hourly."New value: +"Lowest posted pay, a number: annual, or hourly if posted hourly. Feeds the pay floor."
    • changedInput schema / properties / source / description
      Previous value: -"Where it was found: a job site id (linkedin, indeed, company_sites, ...) or referral."New value: +"Where found: job site id (linkedin, indeed, company_sites, ...) or referral; tells the job site like url."
    • changedInput schema / properties / status / description
      Previous value: -"found to work on it (default), or skipped to record a job you won't pursue."New value: +"found (default): to work on; skipped: a job you won't pursue."
    • changedInput schema / properties / status_note / description
      Previous value: -"Why it was skipped, in one plain sentence; for status skipped."New value: +"For skipped: why, one plain sentence."
    • changedInput schema / properties / title / description
      Previous value: -"Job title, as posted."New value: +"As posted."
    • changedInput schema / properties / url / description
      Previous value: -"The posting's URL; also tells which job site it came from."New value: +"Posting URL; tells the job site. The URL just read by freeapply_fetch_posting keeps its keywords."
  2. Addedv1.0.2

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only cover the generic mutation/safety profile, but the description supplies the full decision cascade (already tracked, disallowed/signed-out/paused site, repost match, pay-floor skip), the return shape {job_id, existing, status, rule, earlier} with the meaning of 'earlier' and 'restart', and the missing title/company error. It also discloses the idempotence-like safe-repeat property, which is a mild tension with idempotentHint=false but reads as clarifying the actual state behavior rather than contradicting it.

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 purpose and usage, then a clearly labeled 'Behavior, first match wins' block that prioritizes rules over prose. The telegraphic colon-chained style packs value but is dense enough that an agent must parse carefully to find the branch it 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 16-parameter mutation tool with no output schema, the description covers the refusal conditions, the effective return contract including the 'earlier' list and 'restart' flag, and error behavior. Nothing an agent needs in order to call it correctly and interpret the result appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it explains how status=skipped plus status_note are used together for reviewed-but-unpursued jobs, and how posted pay feeds the pay_floor rule outcome. It stops short of walking through the remaining optional posting fields, which the schema already documents well.

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?

States a specific verb and resource up front ('Claims a job before you work on it') plus the immediate side effects (duplicate check, rules, tracking) and the returned job_id. It also names what it is not by pointing to freeapply_list_jobs for listing and freeapply_update_job for changing, so it is distinguishable from every sibling without opening a 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?

Gives explicit when-to-use ('before opening any application form'), a secondary use case (recording a reviewed job not pursued via status skipped + status_note), and an explicit exclusion ('Not for a job already claimed'). Alternative tools are named for the adjacent operations, leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.