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

by io.github.foundrole

Overview Discussions Admin

Update a tracked job

tracker_update

Destructive

Updates details of a tracked job (notes, deadline, salary, tags).

Input:

tracked_job_id: The tracked job ID — trackedJobs[].id from tracker_list output, distinct from trackable.id and job.id (required)
notes: Updated notes
deadline: Deadline date (ISO 8601 format)
salary_offered: Salary amount
salary_offered_type: Salary type: year, month, week, day, hour
tags: Comma-separated tags (e.g., "remote,startup,tech")
reminder_at: Reminder date/time in ISO 8601 format, e.g. "2025-03-15T10:00:00Z" (must be in the future, or empty to clear)

Output: Returns the updated tracked job.

Input Schema

Name	Required	Description
`tags`	No	Comma-separated tags (e.g., "remote,startup,tech")
`notes`	No	Notes about this job
`deadline`	No	Deadline date in ISO 8601 format
`reminder_at`	No	ISO 8601 datetime, e.g. "2025-03-15T10:00:00Z" (must be in the future, or empty to clear)
`salary_offered`	No	Salary amount
`tracked_job_id`	Yes	The tracked job ID — `trackedJobs[].id` from tracker_list output, distinct from `trackable.id` and `job.id` (required)
`salary_offered_type`	No	Salary type: year, month, week, day, hour

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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

A3.5/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is carried by structured data. The description adds modest value by listing the mutable fields and the reminder 'must be in the future, or empty to clear' rule, but it never addresses the key non-idempotent-update question: whether omitting a field preserves or clears it.

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 header/Input/Output structure front-loads the operation and the fields, and the required ID guidance comes first. It is somewhat verbose because it duplicates the schema field descriptions line for line, but nothing is incoherent or buried.

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 7-parameter mutation tool with full schema coverage and an output schema, the description covers the required ID sourcing, the field set, and the one datetime constraint. The main remaining gap is partial-update semantics for omitted fields, which matters given idempotentHint=false.

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 every parameter is already documented in the schema, and the description largely restates those same descriptions verbatim. It adds no new syntax, format, or interaction detail beyond what the schema provides, so the baseline of 3 applies.

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?

States a specific verb+resource (updates a tracked job) and enumerates which fields can be changed, which implicitly separates it from tracker_update_status and tracker_remove. It never names those siblings explicitly, so the differentiation is inferable rather than stated.

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

Usage Guidelines3/5

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

It usefully tells the agent where the required ID comes from (tracker_list output) and warns it is distinct from trackable.id and job.id, which is real guidance. However, there is no explicit when-to-use vs tracker_update_status, nor any statement of when not to use this tool.

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.