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).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "job_alert_list"
  }
}

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 declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context: results are scoped strictly to the authenticated user (no cross-user access), the page cap is 50 with a default of 20, and each result carries pagination info plus a summary of the underlying job search.

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 scope sentence followed by clearly labeled Input and Output blocks makes it quick to scan. The Input section largely duplicates the schema descriptions, which is mild waste, but nothing is significantly bloated.

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 three-optional-parameter read tool with annotations and an output schema present, the description covers scope, defaults, and output shape adequately. It leaves out what an alert payload contains in detail, but the output schema carries that.

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% and the description's Input block restates the same limit/offset/status text almost verbatim. The only value added is the 'default: all statuses' clarification for `status`, which the schema omits, so this sits just at the baseline.

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?

States a specific verb and resource ('Lists the authenticated user's job alerts') and scopes it precisely to 'all subscription sources (regular, company page, MCP)', which distinguishes it from the job_alert_subscribe/unsubscribe siblings that act on individual alerts.

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 'Lists' and the fact that the sibling tools are mutations. There is no explicit statement of when to prefer this over e.g. tracker_list or jobs_recommendations, and no exclusion guidance, so the agent must infer context.

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.