Skip to main content
Glama

Record what an employer did

freeapply_record_outcome
Idempotent

Record employer responses to job applications—acknowledgements, interviews, rejections, offers—from Gmail emails or manual updates, and update each job's outcome status in FreeApply.

Instructions

Records what an employer did with an application (your side, e.g. applied or skipped: freeapply_update_job). Use: for each employer email found in a reply check, between freeapply_check_replies start and finish, and when the user tells you about a call or corrects an outcome. Not for your own steps. Behavior: with an email (gmail_message_id): stores it; raises the job's outcome only if this email ranks higher than the current one (an interview outranks an acknowledgement); the same gmail_message_id again stores nothing new. Without an email: sets the outcome exactly, whatever its rank. The email fields fill the dashboard's Replies tab. Returns: with an email {recorded (false: recorded before), kind, job_id, outcome (the job's, afterwards)}, job_id and outcome null without job_id; without one {job_id, outcome}. Errors: an unknown job_id; no job_id and no email; an empty outcome with an email.

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": {
      "outcome": "<outcome>"
    },
    "name": "freeapply_record_outcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idNoFrom the reply-check plan or freeapply_list_jobs. Required without an email; with one optional, but without it no outcome changes.
senderNoEmail: sender address.
companyNoEmail: the employer that sent it.
outcomeYesWhat the employer did: acknowledged (automatic 'we received your application' email), replied (a person replied), assessment (test, assignment or screening questionnaire), interview (interview requested or scheduled), rejected (rejection), offer (offer), withdrawn (candidate withdrew); or "" to clear it (without an email only).
subjectNoEmail: subject line.
summaryNoEmail: what it says, one sentence of at most 20 words, no personal data beyond what is needed.
mail_actionNoEmail: what you did with it in Gmail: starred, labeled:<name>, starred+labeled:<name> or none.
received_atNoEmail: when it arrived (ISO 8601).
gmail_thread_idNoEmail: Gmail thread id.
gmail_message_idNoThe employer email's Gmail message id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.0.4
    • changedInput schema / properties / company / description
      Previous value: -"With an email: the employer that sent it."New value: +"Email: the employer that sent it."
    • changedInput schema / properties / gmail_thread_id / description
      Previous value: -"With an email: Gmail thread id."New value: +"Email: Gmail thread id."
    • changedInput schema / properties / job_id / description
      Previous value: -"The job it is about."New value: +"From the reply-check plan or freeapply_list_jobs. Required without an email; with one optional, but without it no outcome changes."
    • changedInput schema / properties / mail_action / description
      Previous value: -"With an email: what you did with it in Gmail."New value: +"Email: what you did with it in Gmail: starred, labeled:<name>, starred+labeled:<name> or none."
    • changedInput schema / properties / outcome / description
      Previous value: -"What the employer did: acknowledged (automatic 'we received your application' email), replied (a person replied), assessment (test, assignment or screening questionnaire), interview (interview requested or scheduled), rejected (rejection), offer (offer), withdrawn (candidate withdrew); or \"\" to clear it."New value: +"What the employer did: acknowledged (automatic 'we received your application' email), replied (a person replied), assessment (test, assignment or screening questionnaire), interview (interview requested or scheduled), rejected (rejection), offer (offer), withdrawn (candidate withdrew); or \"\" to clear it (without an email only)."
    • changedInput schema / properties / received_at / description
      Previous value: -"With an email: when it arrived (ISO 8601)."New value: +"Email: when it arrived (ISO 8601)."
    • changedInput schema / properties / sender / description
      Previous value: -"With an email: sender address."New value: +"Email: sender address."
    • changedInput schema / properties / subject / description
      Previous value: -"With an email: subject line."New value: +"Email: subject line."
    • changedInput schema / properties / summary / description
      Previous value: -"With an email: one sentence on what it says."New value: +"Email: what it says, one sentence of at most 20 words, no personal data beyond what is needed."
  2. Addedv1.0.2

TDQS

A5/5.0
Behavior5/5

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

Beyond the annotations, it explains the rank-based outcome update rule, duplicate-email idempotency, exact-setting behavior without an email, return shapes, and error cases. These details materially help the agent understand side effects and failure modes.

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?

The description is dense but well structured with Use, Behavior, Returns, and Errors sections. It front-loads the core purpose and avoids wasting space on restating schema details.

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?

Given 10 parameters, no output schema, and non-trivial conditional behavior, the description covers usage, side effects, returns, and errors adequately. An agent has enough information to call it correctly in both email and non-email modes.

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

Parameters5/5

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

Although schema coverage is already 100%, the description adds crucial conditional semantics: with gmail_message_id the outcome is rank-gated, without it the outcome is set exactly, and job_id has different implications in each mode. It also explains what the email fields contribute to the dashboard.

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 states a specific verb and resource: recording what an employer did with an application. It also explicitly distinguishes this from the user's own application steps, naming freeapply_update_job as the tool for that.

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 gives explicit trigger conditions: for each employer email found during a reply check, and when the user reports a call or corrects an outcome. It also states what the tool is not for and routes that case to freeapply_update_job.

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