Skip to main content
Glama

Update job status

update_job_status
DestructiveIdempotent

Update a saved job's status, outcome or details. Use status for where the application is now (interviewing, negotiation for an offer, hired). Use outcome for an applied job that ended without progressing: rejected, no_response (no reply after 45+ days), withdrawn, or didnt_apply; status stays as it is. With didnt_apply, give a reason: job_closed reports the listing as expired, and the rest improve the user's future matches. Add detail for anything worth knowing (what the page said, a hidden requirement). Uses the connected Himalayas account; no extra sign-in needed.

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": {
      "id": "<id>"
    },
    "name": "update_job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesKanban item ID
notesNoUpdated notes
detailNoAnything worth knowing about the outcome, in a sentence or two. No personal data.
reasonNoWhy the user didn't apply (only with outcome didnt_apply)
statusNoNew application status
outcomeNoWhat happened after applying, as reported by the user. "clear" removes a recorded outcome.
excitementNoExcitement level from 0-5

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / detail
      Added value: +{
      +  "description": "Anything worth knowing about the outcome, in a sentence or two. No personal data.",
      +  "maxLength": 500,
      +  "type": "string"
      +}
    • addedInput schema / properties / reason
      Added value: +{
      +  "description": "Why the user didn't apply (only with outcome didnt_apply)",
      +  "enum": [
      +    "job_closed",
      +    "needs_account",
      +    "location_or_visa_restricted",
      +    "pay_too_low",
      +    "wrong_timezone",
      +    "not_really_remote",
      +    "wrong_seniority",
      +    "wrong_role",
      +    "not_interested",
      +    "other"
      +  ],
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / outcome
      Added value: +{
      +  "description": "What happened after applying, as reported by the user. \"clear\" removes a recorded outcome.",
      +  "enum": [
      +    "rejected",
      +    "no_response",
      +    "withdrawn",
      +    "didnt_apply",
      +    "clear"
      +  ],
      +  "type": "string"
      +}
  3. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  4. 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 and idempotentHint=true; the description adds real context beyond them, including the auth model ("Uses the connected Himalayas account; no extra sign-in needed") and the non-obvious state rule that outcome leaves status untouched. It doesn't spell out exactly which destructive action the hint refers to beyond the "clear" removal, so a 4.

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?

Purpose is front-loaded in the first sentence, followed by compact field-by-field guidance, and the auth note is a single short clause. It is slightly dense for a description, but each sentence carries actionable content and nothing is redundant.

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?

With 7 parameters, three enums, no output schema and no nested objects, the description supplies the conditional logic an agent needs (when to send status vs outcome vs reason) and covers auth. The remaining gap is mutation mechanics — what happens to omitted fields like notes and excitement — which is left to inference.

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. The description goes beyond the schema by encoding cross-parameter relationships the schema cannot express: outcome vs status precedence, reason being conditional on didnt_apply, and the semantic difference between reason values that report an expired listing versus those that improve future matches.

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+resource ("Update a saved job's status, outcome or details") and scopes it to saved jobs, distinguishing it from update_company_job, update_profile and the many other update_* siblings. An agent can identify the target entity and the mutated fields without opening the 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?

Gives unusually explicit field-selection guidance: status is for where the application stands now, outcome is for applied jobs that ended without progressing, and reason is only valid with didnt_apply. It doesn't name alternative tools or state when not to call this tool, so it stops short of a 5.

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