FoundRole — AI Job Search & Application Tracker MCP for Claude & ChatGPT

by io.github.foundrole

Overview Discussions Admin

Move a tracked job to another stage

tracker_update_status

Destructive

Updates the status of a tracked job.

Input:

tracked_job_id: The tracked job ID — trackedJobs[].id from tracker_list output, distinct from trackable.id and job.id (required)
status: New status: saved, applied, interviewing, offered, archived (required)
sub_status: Sub-status within the main status, valid only for that status (optional): saved: interested, researching_company, preparing_application, ready_to_apply; applied: application_submitted, followed_up; interviewing: interview_scheduled, phone_screen, technical, onsite, final_round, pending_feedback; offered: negotiating, considering, offer_received, accepted; archived: ghosted, rejected_by_company, withdrawn_by_candidate, not_interested, employed_by_this_company, employed_by_another_company

Output: Returns the updated tracked job.

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": {
      "tracked_job_id": "<tracked_job_id>",
      "status": "<status>"
    },
    "name": "tracker_update_status"
  }
}

Input Schema

Name	Required	Description
`status`	Yes	New status: saved, applied, interviewing, offered, archived
`sub_status`	No	Sub-status within the main status, valid only for that status — saved: interested, researching_company, preparing_application, ready_to_apply; applied: application_submitted, followed_up; interviewing: interview_scheduled, phone_screen, technical, onsite, final_round, pending_feedback; offered: negotiating, considering, offer_received, accepted; archived: ghosted, rejected_by_company, withdrawn_by_candidate, not_interested, employed_by_this_company, employed_by_another_company
`tracked_job_id`	Yes	The tracked job ID — `trackedJobs[].id` from tracker_list output, distinct from `trackable.id` and `job.id` (required)

Output Schema

Name	Required	Description	Default
`hasMore`	No
`totalCount`	No
`trackedJob`	No
`statusOrder`	No
`trackedJobs`	No
`figureSources`	No
`trackerWebUrl`	No
`subStatusOrder`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 10, 2026

addedOutput schema / properties / trackedJob / properties / appliedDateUnknown

Added value: +{
+  "description": "True for a job at the applied status with no stored applied date, unless the person said they do not remember it. FoundRole never fills that date in by itself; it comes from the person and tracker_update stores it in applied_at, or records in applied_date_declined that they do not remember it.",
+  "type": "boolean"
+}

addedOutput schema / properties / trackedJob / properties / daysSinceApplied

Added value: +{
+  "description": "Whole days since the applied date, counted in the user's time zone; null without an applied date.",
+  "type": [
+    "integer",
+    "null"
+  ]
+}

addedOutput schema / properties / trackedJob / properties / followUpDay

Added value: +{
+  "description": "Latest follow-up point, in days after applying, that a job still at the applied status has reached; null before the first point and for every other status. FoundRole never moves or archives a job by itself.",
+  "enum": [
+    7,
+    14,
+    21,
+    null
+  ],
+  "type": [
+    "integer",
+    "null"
+  ]
+}

addedOutput schema / properties / trackedJobs / items / properties / appliedDateUnknown

Added value: +{
+  "description": "True for a job at the applied status with no stored applied date, unless the person said they do not remember it. FoundRole never fills that date in by itself; it comes from the person and tracker_update stores it in applied_at, or records in applied_date_declined that they do not remember it.",
+  "type": "boolean"
+}

addedOutput schema / properties / trackedJobs / items / properties / daysSinceApplied

Added value: +{
+  "description": "Whole days since the applied date, counted in the user's time zone; null without an applied date.",
+  "type": [
+    "integer",
+    "null"
+  ]
+}

addedOutput schema / properties / trackedJobs / items / properties / followUpDay

Added value: +{
+  "description": "Latest follow-up point, in days after applying, that a job still at the applied status has reached; null before the first point and for every other status. FoundRole never moves or archives a job by itself.",
+  "enum": [
+    7,
+    14,
+    21,
+    null
+  ],
+  "type": [
+    "integer",
+    "null"
+  ]
+}

Changed1 schema field changedNov 3, 2026

addedOutput schema / properties / figureSources

Added value: +{
+  "properties": {
+    "estimatedSalary": {
+      "properties": {
+        "basis": {
+          "type": "string"
+        },
+        "methodologyUrl": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "ghostScore": {
+      "properties": {
+        "basis": {
+          "type": "string"
+        },
+        "methodologyUrl": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "methodologyUrl": {
+      "type": "string"
+    },
+    "source": {
+      "enum": [
+        "FoundRole"
+      ],
+      "type": "string"
+    },
+    "visaRecords": {
+      "properties": {
+        "basis": {
+          "type": "string"
+        },
+        "falseMeans": {
+          "type": "string"
+        },
+        "methodologyUrl": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": [
+    "object",
+    "null"
+  ]
+}

Changed1 schema field changedJul 22, 2026

changedInput schema / properties / sub_status / description

Previous value: -"Sub-status within the main status"New value: +"Sub-status within the main status, valid only for that status — saved: interested, researching_company, preparing_application, ready_to_apply; applied: application_submitted, followed_up; interviewing: interview_scheduled, phone_screen, technical, onsite, final_round, pending_feedback; offered: negotiating, considering, offer_received, accepted; archived: ghosted, rejected_by_company, withdrawn_by_candidate, not_interested, employed_by_this_company, employed_by_another_company"

Changed16 schema fields changedJul 21, 2026
- changedOutput schema / properties / trackedJob / properties / appliedAt / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / trackedJob / properties / createdAt / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / trackedJob / properties / deadline / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / trackedJob / properties / notes / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / trackedJob / properties / reminderAt / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / trackedJob / properties / salaryOfferedType / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / trackedJob / properties / subStatus / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / trackedJob / properties / updatedAt / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / trackedJobs / items / properties / appliedAt / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / trackedJobs / items / properties / createdAt / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / trackedJobs / items / properties / deadline / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / trackedJobs / items / properties / notes / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / trackedJobs / items / properties / reminderAt / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / trackedJobs / items / properties / salaryOfferedType / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / trackedJobs / items / properties / subStatus / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / trackedJobs / items / properties / updatedAt / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

Changed3 schema fields changedJul 20, 2026

addedInput schema / $schema

Added value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

addedOutput schema / $schema

Added value: +"https://json-schema.org/draft/2020-12/schema"

Changed6 schema fields changedJul 15, 2026

addedOutput schema / properties / hasMore
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / statusOrder

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / subStatusOrder
```
Added value: +{
+  "type": "object"
+}
```
addedOutput schema / properties / totalCount
```
Added value: +{
+  "type": "integer"
+}
```

addedOutput schema / properties / trackedJobs

Added value: +{
+  "items": {
+    "properties": {
+      "appliedAt": {
+        "type": "string"
+      },
+      "contacts": {
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "createdAt": {
+        "type": "string"
+      },
+      "deadline": {
+        "type": "string"
+      },
+      "id": {
+        "type": "string"
+      },
+      "isStarred": {
+        "type": "boolean"
+      },
+      "job": {
+        "type": [
+          "object",
+          "null"
+        ]
+      },
+      "notes": {
+        "type": "string"
+      },
+      "reminderAt": {
+        "type": "string"
+      },
+      "salaryOffered": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "salaryOfferedType": {
+        "type": "string"
+      },
+      "status": {
+        "type": "string"
+      },
+      "subStatus": {
+        "type": "string"
+      },
+      "tags": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "trackable": {
+        "type": [
+          "object",
+          "null"
+        ]
+      },
+      "updatedAt": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / trackerWebUrl
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedJun 14, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "trackedJob": {
+      "properties": {
+        "appliedAt": {
+          "type": "string"
+        },
+        "contacts": {
+          "items": {
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "createdAt": {
+          "type": "string"
+        },
+        "deadline": {
+          "type": "string"
+        },
+        "id": {
+          "type": "string"
+        },
+        "isStarred": {
+          "type": "boolean"
+        },
+        "notes": {
+          "type": "string"
+        },
+        "reminderAt": {
+          "type": "string"
+        },
+        "salaryOffered": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "salaryOfferedType": {
+          "type": "string"
+        },
+        "status": {
+          "type": "string"
+        },
+        "subStatus": {
+          "type": "string"
+        },
+        "tags": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "trackable": {
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "updatedAt": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "id"
+      ],
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedJun 10, 2026

changedInput schema / properties / tracked_job_id / description

Previous value: -"The tracked job ID"New value: +"The tracked job ID — `trackedJobs[].id` from tracker_list output, distinct from `trackable.id` and `job.id` (required)"

First observedJun 3, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the agent knows this mutates state and is not idempotent. The description adds useful semantic context through the sub_status validity matrix, but it says nothing about consequences (e.g., whether sub_status is cleared when switching status, whether an archived job can be moved back) beyond 'Returns the updated tracked job.'

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 purpose sentence followed by structured Input/Output sections; the long sub_status enumeration is dense but genuinely necessary given there are no enums in the schema. The output line is thin but the output schema exists, so it earns its place.

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?

For a 3-parameter mutation with full schema coverage and an output schema, the description gives the agent everything needed to construct a valid call, including the status-to-sub_status relationship. It falls short on behavioral edge cases and on routing guidance versus tracker_update, which is the main remaining gap.

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 would be 3; however the description adds real meaning by spelling out the full enum-like value sets and, critically, that sub_status is 'valid only for that status' and cross-mapping each sub_status to its parent status. It also clarifies the ambiguous tracked_job_id versus trackable.id and job.id distinction, which the schema states but the description reinforces prominently.

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 ('Updates the status of a tracked job') and the title reinforces it as a stage move. It clearly distinguishes itself from tracker_update, which would presumably handle other fields, though it never names that sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance on when to use this tool versus tracker_update or tracker_add, and no mention of preconditions or when a status change should not be made. The only implied usage is that it's for status transitions, which an agent must infer from the purpose line.

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

All FoundRole — AI Job Search & Application Tracker MCP for Claude & ChatGPT tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.