Skip to main content
Glama
jobhunt

jobhunt

by athulanish

update_job_status

Update a saved job application's status and optional notes, marking it applied only after you confirm you submitted it yourself.

Instructions

Update a saved job's status and optionally its notes. Only mark 'applied' after the user says they submitted it themselves.

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": "update_job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNo
job_idYes
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose one behavioral constraint (the 'applied' guard), which goes beyond what the schema conveys. However, it says nothing about whether status transitions are validated, whether omitting notes overwrites existing notes (the schema defaults notes to an empty string), what permissions are required, or whether the change is reversible.

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?

Two short sentences, with the primary action stated first and the safety rule second. There is no filler and every sentence carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations, no output schema, and 0% parameter description coverage across three parameters, the definition leaves too much open. The biggest gap is the missing set of valid status values and the unclear effect of the notes default on existing data, both of which an agent needs in order to call this correctly.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate, and it only partially does. It adds meaning for status and notes ('optionally'), but never explains job_id, and critically never lists the valid status values even though status is a free-form string with no enum. An agent must guess the acceptable status strings.

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?

The description states a specific verb and resource: 'Update a saved job's status and optionally its notes.' That is enough to distinguish it from get_job, list_jobs, and save_job. It stops short of explicitly differentiating itself from sibling tools that also modify jobs, which keeps it at 4 rather than 5.

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?

It gives a concrete conditional rule: only mark 'applied' after the user confirms they submitted the application themselves. That is real when-to-use guidance rather than an implied convention. It does not mention alternatives (for example, using save_job to create the record first) or exclusions for other status values.

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