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

by io.github.foundrole

Overview Discussions Admin

Remove a job from the tracker

tracker_remove

Destructive

Removes a job from the user's job tracker.

Input:

tracked_job_id: The tracked job ID — trackedJobs[].id from tracker_list output, distinct from trackable.id and job.id (required)

Output: Confirms the job was removed from tracking.

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>"
    },
    "name": "tracker_remove"
  }
}

Input Schema

Name	Required	Description	Default
`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"
+  ]
+}

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 to remove"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, readOnlyHint=false and idempotentHint=false, so the safety profile is covered. The description adds a light behavioral note ('removes from tracking' implies the job itself survives, and output confirms the removal), but says nothing about irreversibility or what happens on a repeat call, which matters given idempotentHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead sentence is front-loaded and the Input/Output blocks are scannable. However, the Input bullet is a verbatim duplication of the schema description, and the Output block largely restates what the output schema already conveys, so a third of the text does not earn 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 one-parameter tool with full schema coverage, an output schema, and complete annotations, little is missing. The remaining gap — post-removal state and repeat-call behavior — is minor relative to the tool's simplicity.

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 coverage is 100%, so the schema already documents tracked_job_id. The description reproduces the same sentence verbatim — including the useful disambiguation from trackable.id and job.id — but adds no meaning beyond the schema, which is the baseline 3 case.

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 and resource: 'Removes a job from the user's job tracker.' An agent can tell this apart from tracker_add/tracker_update by the verb alone. It stops short of naming a sibling or stating what is *not* affected, but the purpose is unambiguous.

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?

Usage is only implied by the verb — the description never states when to prefer this over tracker_update or tracker_list, nor explicitly that the underlying job posting is not deleted, only the tracking record. There are no exclusions or prerequisites given.

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.