Skip to main content
Glama

add_application

Log jobs you found yourself—referrals, recruiter or LinkedIn links—as applied, queued, or new, so applications and next steps stay in one place.

Instructions

Add a job jobwatch didn't find (a referral, a recruiter, LinkedIn...), so everything is in one place: an application (only after the person has applied themselves), or status queued for one they're considering. A url to one job on Greenhouse, Lever, Ashby, Workable, Workday, Rippling, Google Careers (a .../jobs/results/ link), amazon.jobs (a .../jobs/ link), Oracle Recruiting Cloud (an ...oraclecloud.com/.../sites//job/ link), SmartRecruiters (a jobs.smartrecruiters.com// link), an Avature portal (a .../JobDetail// link) or iCIMS (a .../jobs///job link) or Jobvite (a jobs.jobvite.com//job/ link) or a careers site's job page (a .../jobs// link whose page has JobPosting markup) is read in full (company and title may be left out). A LinkedIn job link is never read (LinkedIn's robots.txt disallows it): give company and title with it (and text to score it), and it's tracked on the company's own board when the same job is found there. Otherwise give company and title, and text (the posting, pasted) so it can be scored. For a job jobwatch already tracks (it came from get_digest or get_job), use mark_job instead; for the jobs in job-alert emails, import_job_alerts. When it's (maybe) the same opening as one already applied to, queued or skipped, the reply ends with that warning: tell the person.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "add_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoA link to the job: Greenhouse, Lever, Ashby, Workable, Workday, Rippling, Google Careers, amazon.jobs, Oracle Recruiting Cloud, SmartRecruiters, Avature, iCIMS, Jobvite, a careers site's job page (JobPosting markup) or LinkedIn are read in full; any other link is just kept.
noteNoA note: who referred them, how they found it...
textNoThe posting's text, pasted, when the link can't be read, so it can be scored and prepped.
titleNoThe job title; may be left out when url is a job link it can read.
statusNoapplied (the default; only once the person has applied themselves), new to just track a job as a fresh find to judge later (it shows in get_digest, nothing applied), queued for one they're considering, or a later stage such as interviewing.applied
companyNoThe company; may be left out when url is a job link it can read.
follow_upNoA day: YYYY-MM-DD, or +N for N days from today. An empty string clears it.
next_stepNoWhat happens next ("hiring manager call Friday").
applied_onNoThe day applied (YYYY-MM-DD), if not today.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.10.0
    • changedInput schema / properties / status / description
      Previous value: -"applied (the default; only once the person has applied themselves), queued for one they're considering, or a later stage such as interviewing."New value: +"applied (the default; only once the person has applied themselves), new to just track a job as a fresh find to judge later (it shows in get_digest, nothing applied), queued for one they're considering, or a later stage such as interviewing."
    • changedInput schema / properties / url / description
      Previous value: -"A link to the job: Greenhouse, Lever, Ashby, Workable, Workday, Rippling, Google Careers, amazon.jobs, Oracle Recruiting Cloud, SmartRecruiters, Avature, iCIMS, Jobvite or LinkedIn are read in full; any other link is just kept."New value: +"A link to the job: Greenhouse, Lever, Ashby, Workable, Workday, Rippling, Google Careers, amazon.jobs, Oracle Recruiting Cloud, SmartRecruiters, Avature, iCIMS, Jobvite, a careers site's job page (JobPosting markup) or LinkedIn are read in full; any other link is just kept."
  2. Changed1 schema field changedv0.6.0
    • changedInput schema / properties / url / description
      Previous value: -"A link to the job: Greenhouse, Lever, Ashby, Workable, Workday, Rippling, Google Careers, amazon.jobs, Oracle Recruiting Cloud, SmartRecruiters, Avature, iCIMS or LinkedIn are read in full; any other link is just kept."New value: +"A link to the job: Greenhouse, Lever, Ashby, Workable, Workday, Rippling, Google Careers, amazon.jobs, Oracle Recruiting Cloud, SmartRecruiters, Avature, iCIMS, Jobvite or LinkedIn are read in full; any other link is just kept."
  3. Changed1 schema field changedv0.5.0
    • changedInput schema / properties / url / description
      Previous value: -"A link to the job: Greenhouse, Lever, Ashby, Workable, Workday, Rippling or LinkedIn are read in full; any other link is just kept."New value: +"A link to the job: Greenhouse, Lever, Ashby, Workable, Workday, Rippling, Google Careers, amazon.jobs, Oracle Recruiting Cloud, SmartRecruiters, Avature, iCIMS or LinkedIn are read in full; any other link is just kept."
  4. Changed9 schema fields changedv0.2.3
    • addedInput schema / properties / applied_on / description
      Added value: +"The day applied (YYYY-MM-DD), if not today."
    • addedInput schema / properties / company / description
      Added value: +"The company; may be left out when url is a job link it can read."
    • addedInput schema / properties / follow_up / description
      Added value: +"A day: YYYY-MM-DD, or +N for N days from today. An empty string clears it."
    • addedInput schema / properties / next_step / description
      Added value: +"What happens next (\"hiring manager call Friday\")."
    • addedInput schema / properties / note / description
      Added value: +"A note: who referred them, how they found it..."
    • addedInput schema / properties / status / description
      Added value: +"applied (the default; only once the person has applied themselves), queued for one they're considering, or a later stage such as interviewing."
    • addedInput schema / properties / text / description
      Added value: +"The posting's text, pasted, when the link can't be read, so it can be scored and prepped."
    • addedInput schema / properties / title / description
      Added value: +"The job title; may be left out when url is a job link it can read."
    • addedInput schema / properties / url / description
      Added value: +"A link to the job: Greenhouse, Lever, Ashby, Workable, Workday, Rippling or LinkedIn are read in full; any other link is just kept."
  5. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With annotations declaring readOnlyHint=false and openWorldHint=true, the description still adds real behavioral context: which URL hosts are fetched and parsed versus merely stored, that LinkedIn links are never fetched because robots.txt disallows it, and that the reply may end with a duplicate-opening warning the agent must relay. It does not cover failure modes for unreadable links beyond the LinkedIn case, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The scoping and sibling routing are front-loaded, which is good, but the middle is a dense run-on with nested parentheticals and a long 'or ... or ...' provider chain that repeats the schema's url description. Several clauses could be trimmed with no loss of meaning.

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 9-parameter, zero-required mutation tool this covers a lot: status lifecycle, link-reading behavior, LinkedIn exception, and sibling alternatives, and an output schema exists so return values need no explanation. The gap is that nothing says what the minimum viable call is when neither a readable url nor company+title+text is supplied, so the all-optional schema is left ambiguous.

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%, so the baseline is 3, and much of the description's parameter content duplicates the schema — the provider enumeration and status meanings are repeated nearly verbatim. One genuinely additive point is that a LinkedIn link is 'never read' and needs company/title/text supplied, which actually corrects the schema's claim that LinkedIn links 'are read in full'.

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 opening states a specific verb and resource — 'Add a job jobwatch didn't find' — and immediately narrows scope ('a referral, a recruiter, LinkedIn'). It also names the two siblings that handle adjacent cases (mark_job for already-tracked jobs, import_job_alerts for alert emails), so an agent can route 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?

Explicit when-to-use and when-not-to-use: 'For a job jobwatch already tracks (it came from get_digest or get_job), use mark_job instead; for the jobs in job-alert emails, import_job_alerts.' It also states the precondition for the default status ('only after the person has applied themselves') and what to do with the duplicate warning.

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