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

List job alerts

job_alert_list

Read-only

Lists the authenticated user's job alerts across all subscription sources (regular, company page, MCP).

Input:

status: Filter by status — one of pending, active, unsubscribed (optional, default: all statuses)
limit: Number of results to return (default 20, max 50)
offset: Number of results to skip (default 0)

Output: Returns the user's job alerts with pagination info and a summary of the underlying job search (query, location, company where available). 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 to return (default 20, max 50)
`offset`	No	Number of results to skip (default 0)
`status`	No	Filter by status: pending, active, unsubscribed

Output Schema

Name	Required	Description	Default
`hasMore`	No
`jobAlerts`	No
`totalCount`	No
`frequencies`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 8, 2026
- addedOutput schema / properties / jobAlerts / items / properties / delivery
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / jobAlerts / items / properties / fastActive
```
Added value: +{
+  "type": "boolean"
+}
```

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 changedJun 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "frequencies": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "hasMore": {
+      "type": "boolean"
+    },
+    "jobAlerts": {
+      "items": {
+        "properties": {
+          "createdAt": {
+            "type": "string"
+          },
+          "frequency": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "jobSearch": {
+            "type": [
+              "object",
+              "null"
+            ]
+          },
+          "lastSentAt": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "status": {
+            "type": "string"
+          },
+          "subscriptionSource": {
+            "type": "string"
+          },
+          "updatedAt": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "totalCount": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedJun 9, 2026

changedInput schema / properties / status / description

Previous value: -"Filter by status: active, pending, unsubscribed"New value: +"Filter by status: pending, active, unsubscribed"

First observedJun 3, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower, and the description adds real behavioral context: responses carry pagination info, a summary of the underlying job search (query, location, company), and a system_instruction governing how results should be presented for the current client. That presentation-instruction detail is not derivable from 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?

Front-loaded purpose sentence followed by clearly labeled Input/Output blocks; the structure aids scanning. It is slightly padded by restating parameter text already present in the schema.

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 low-risk, zero-required-parameter list tool with a full output schema and covering annotations, this is close to complete. Return-value detail is technically redundant given the output schema, but the mention of the system_instruction field adds genuine completeness.

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 limit, offset and status, and the description largely repeats them. It does add one piece of meaning the schema omits — that status is optional and defaults to all statuses — but nothing about syntax beyond that.

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?

The opening sentence states a specific verb (Lists), resource (job alerts), owner scope (authenticated user's) and breadth (all subscription sources: regular, company page, MCP). This clearly distinguishes it from the job_alert_subscribe/unsubscribe siblings without needing their schemas.

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 implied — you call this to enumerate the user's existing alerts — and the sibling mutations (subscribe/unsubscribe) are obviously different operations. However, the description never states when to prefer this over e.g. job_alert_unsubscribe_all or tracker_list, nor any preconditions or exclusions.

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.