Skip to main content
Glama

toggle_job_application_interest

Destructive

Use this tool when the user says "not interested", "no longer interested", "withdraw interest", "I'm out", "remove from pipeline", or any equivalent phrase. This is the ONLY correct tool for withdrawing interest — do not use update_job_application_status as a proxy.

Deactivates an active application (or reactivates a previously deactivated one). Mirrors the "I am no longer interested in this role" button in the GigHQ app.

Pass currentIsActive: true to deactivate an active application:

  • Stamps an end date on the current status stage (appliedEndDate, interviewingEndDate, or offerEndDate)

  • Sets status to CANDIDATE_WITHDREW and sets endDate = now

Pass currentIsActive: false to reactivate a previously deactivated application:

  • Clears endDate and resets status to APPLIED

Check the current isActive value with get_job_application or search_job_applications before calling.

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": {
      "uuid": "<uuid>",
      "currentIsActive": "<currentIsActive>",
      "context": "<context>"
    },
    "name": "toggle_job_application_interest"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesThe UUID of the job application to update (the 'uuid' field, not the numeric 'id').
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.
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.
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.
currentIsActiveYesThe current active state of the application. Pass true if the application is currently active (this will deactivate it); pass false if it is currently inactive (this will reactivate it). Retrieve this value from get_job_application or search_job_applications first.

Output Schema

NameRequiredDescriptionDefault
resultYes
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: -[
      -  "uuid",
      -  "currentIsActive"
      -]New value: +[
      +  "uuid",
      +  "currentIsActive",
      +  "context"
      +]
  2. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / required
      Previous value: -[
      -  "message"
      -]New value: +[
      +  "message",
      +  "result"
      +]
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare destructive and non-read-only, and the description supplies the missing detail: exactly what state changes (end dates stamped, status set to CANDIDATE_WITHDREW, endDate = now) and what the reverse path does (clears endDate, resets to APPLIED). This is substantive behavioral disclosure beyond the annotation flags.

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?

Front-loaded with the routing condition and the exclusion before the mechanics, then bullets split the two branches cleanly. The trigger-phrase list is long but functional; overall the text is efficient for a destructive toggle, with only mild redundancy between the opening sentence and the 'Mirrors the button' line.

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 two-direction toggle with an output schema already present, the description covers prerequisites, both branches' effects, and sibling avoidance. An agent has everything needed to call it correctly without guessing.

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 baseline is 3, but the description goes further by explaining the consequence of each currentIsActive value — stamping stage end dates and setting CANDIDATE_WITHDREW versus clearing endDate and resetting to APPLIED. It adds outcome semantics the schema only hints at, though it says nothing about the analytics-only parameters (context, llm_model, conversation_id).

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 and resource — deactivating or reactivating a job application's interest — and explicitly names the sibling tool (update_job_application_status) that it must not be confused with. It also anchors the behavior to the 'I am no longer interested in this role' button, so the agent knows exactly which operation this is.

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?

Gives concrete trigger phrases, an explicit exclusion ('do not use update_job_application_status as a proxy'), and a prerequisite step ('Check the current isActive value with get_job_application or search_job_applications before calling'). When-to-use, when-not-to-use, and alternatives are all covered.

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.