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

List tracked jobs

tracker_list

Read-only

Lists the user's tracked jobs with optional filtering and pagination.

Input:

status: Filter by status (saved, applied, interviewing, offered, archived)
limit: Number of results per page (default 20, max 50)
offset: Number of results to skip (default 0)

Output: Returns a list of tracked jobs grouped by status with pagination info. Each response includes a system_instruction describing how to present the results for the current client.

Input Schema

Name	Required	Description
`limit`	No	Number of results per page (default 20, max 50)
`offset`	No	Number of results to skip (default 0)
`status`	No	Filter by status: saved, applied, interviewing, offered, archived

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"

Changed1 schema field changedJul 15, 2026

addedOutput schema / properties / trackedJob

Added value: +{
+  "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"
+}

Changed1 schema field changedJun 13, 2026
- addedOutput schema / properties / trackerWebUrl
```
Added value: +{
+  "type": "string"
+}
```
Changed1 schema field changedJun 10, 2026
- addedOutput schema / properties / subStatusOrder
```
Added value: +{
+  "type": "object"
+}
```
Changed1 schema field changedJun 10, 2026
- addedOutput schema / properties / trackedJobs / items / properties / job
```
Added value: +{
+  "type": [
+    "object",
+    "null"
+  ]
+}
```

Changed1 schema field changedJun 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "hasMore": {
+      "type": "boolean"
+    },
+    "statusOrder": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "totalCount": {
+      "type": "integer"
+    },
+    "trackedJobs": {
+      "items": {
+        "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": "array"
+    }
+  },
+  "type": "object"
+}

First observedJun 3, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: results are grouped by status and each response carries a system_instruction on how to present results for the current client, which is not derivable from the input schema or annotations.

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 layout is front-loaded and scannable with clear Input/Output sections, and the opening sentence carries the core purpose. The Input block largely duplicates the schema, which costs a little, but the overall size is appropriate.

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 read-only, no-required-parameter list tool with a rich input schema, annotations, and an output schema, the description covers purpose, parameters, and return shape adequately. The only real omission is routing guidance versus sibling tracker_* and job_alert_* tools.

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 three parameters, their defaults, and bounds. The description restates the same information verbatim (status values, default 20/max 50, default 0) without adding format, syntax, or edge-case meaning, so baseline 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?

The description states a specific verb and resource ('Lists the user's tracked jobs') with scope details (filtering, pagination). It is clear what the tool returns, but it never distinguishes itself from sibling read tools like job_alert_list or jobs_search, so an agent must infer the boundary from the name alone.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as job_alert_list or jobs_search. The mention of 'optional filtering and pagination' describes behavior rather than the conditions under which this tool should be chosen.

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.