Skip to main content
Glama

update_job_application_note

Destructive

Updates the body or category of an existing job application note. Both body and category are required — the backend replaces the full note on update.

If the user only mentions updating the body and doesn't specify a category, infer the best-fit category from the note content using this mapping: • text_message — contact via SMS/text • email_external — contact via email • call — phone or video call • linkedin_connection_request — sent or received a LinkedIn connection request • linkedin_message — direct message on LinkedIn • coffee_chat — informational interview or coffee chat • in_person_meeting — face-to-face meeting • networking_event — conference, meetup, career fair, or similar event • referral — someone referred the user or made an introduction • other — genuinely doesn't fit any of the above

If ambiguous, ask the user to confirm before calling. Use list_job_application_notes to retrieve the note UUID if you don't have it.

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": {
      "note_uuid": "<note_uuid>",
      "application_id": "<application_id>",
      "body": "<body>",
      "category": "<category>",
      "context": "<context>"
    },
    "name": "update_job_application_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesUpdated note text. Max 3000 characters.
contextYesA few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as "a customer". Do not quote the user or include names, emails, or other personal details.
categoryYesCategory tag for the note. Use a slug from the tool description (e.g. 'call', 'in_person_meeting'). Display labels like 'Call' or 'In-Person Meeting' are also accepted.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
note_uuidYesUUID of the note to update. Returned by add_job_application_note or list_job_application_notes.
application_idYesUUID of the job application this note belongs to.
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Output Schema

NameRequiredDescriptionDefault
uuidNo
appUrlYes
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "A few words on why you are calling this tool, for the server developer's analytics. Describe people and things by role, such as \"a customer\". Do not quote the user or include names, emails, or other personal details.",
      +  "type": "string"
      +}
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "The model identifier you are running as, for example \"claude-opus-4-8\" or \"gpt-5.2\". Pass \"unknown\" if you are not certain. Recorded for the server developer's analytics.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "note_uuid",
      -  "application_id",
      -  "body",
      -  "category"
      -]New value: +[
      +  "note_uuid",
      +  "application_id",
      +  "body",
      +  "category",
      +  "context"
      +]
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Discloses the single most important behavior the annotations cannot express: both body and category are required because 'the backend replaces the full note on update,' so an agent knows a partial edit will overwrite unspecified fields. This is consistent with destructiveHint=true and adds real operational consequence. It also front-loads the prerequisite retrieval path for the UUID.

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?

The key constraint (full replacement, both fields required) is front-loaded ahead of everything else, and the category bullets each map to a distinct value with no filler. The taxonomy is long but load-bearing since the schema defines no enum, so the length is justified rather than wasteful.

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 destructive seven-parameter mutation with annotations and an output schema, the description covers the overwrite risk, the category taxonomy, and the UUID prerequisite — the three things an agent could get wrong. Return values need not be explained given the output schema exists, and the remaining unknown (behavior when the note UUID is not found) is minor.

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 description coverage is 100%, so the schema already documents all seven parameters, which sets the baseline at 3. The description does add real meaning by supplying the complete category taxonomy that the schema explicitly points back to ('Use a slug from the tool description') and by explaining the UUID provenance. It says nothing about application_id needing to match the note's existing application, a gap the schema does not fill either.

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?

Opens with a specific verb and resource: 'Updates the body or category of an existing job application note.' It immediately clarifies that this is a full-replacement update, and names list_job_application_notes as the source of the note UUID. It stops short of explicitly contrasting itself with add_job_application_note or delete_job_application_note, which is the only thing keeping it from a 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?

Gives concrete preconditions and a decision procedure: if the user supplies only a body, infer category via the supplied mapping; if ambiguous, ask the user before calling; use list_job_application_notes to obtain the UUID. It does not state when an agent should instead use add/delete note tools, so the update-vs-create boundary is left implicit.

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.