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

Unsubscribe from all job alerts

job_alert_unsubscribe_all

DestructiveIdempotent

Unsubscribes the authenticated user from ALL of their job alerts at once, across every subscription source (regular, company page, MCP).

Input:

confirm: Must be true to execute. The call is rejected when omitted or not true — this guards against an unintended bulk unsubscribe.

Output: Confirms how many alerts were unsubscribed, beside the user's current job alerts in the same shape and order as the first page of job_alert_list. Idempotent: returns success even when the user has no active alerts.

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": {
      "confirm": "<confirm>"
    },
    "name": "job_alert_unsubscribe_all"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	Yes	Set to true to confirm unsubscribing from every alert; the call is rejected otherwise

Output Schema

Name	Required	Description	Default
`hasMore`	No
`message`	No
`success`	Yes
`jobAlerts`	No
`totalCount`	No
`frequencies`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 7, 2026

addedOutput schema / properties / frequencies

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / hasMore
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / jobAlerts

Added value: +{
+  "items": {
+    "properties": {
+      "createdAt": {
+        "type": "string"
+      },
+      "delivery": {
+        "type": "string"
+      },
+      "fastActive": {
+        "type": "boolean"
+      },
+      "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"
+}

addedOutput schema / properties / totalCount
```
Added value: +{
+  "type": "integer"
+}
```

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 14, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "message": {
+      "type": "string"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}

AddedJun 13, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare destructive and idempotent, but the description adds real context beyond them: the confirm guard exists specifically to prevent unintended bulk unsubscribe, and the call is rejected when confirm is omitted. It also discloses the no-active-alerts edge case and the response contents, which annotations alone cannot convey.

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

Conciseness5/5

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

The operation statement is front-loaded, then Input and Output are separated into clearly labeled blocks, and the idempotency note lands where a caller would look for it. Every sentence carries informational weight; nothing is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, one-parameter bulk mutation, the description covers the guard requirement, the failure mode, the empty-state behavior, and the response contents. Even though an output schema exists (so return details are optional), the description is complete for an agent to call it safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter is already documented, so the baseline is 3. The description earns an extra point by explaining the intent of confirm (a safety guard against accidental bulk unsubscribe) and the rejection behavior, adding rationale beyond the schema's wording.

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 description opens with a specific verb and resource ("Unsubscribes the authenticated user from ALL of their job alerts") and scopes it further ("across every subscription source (regular, company page, MCP)"). The word ALL distinguishes it clearly from the singular job_alert_unsubscribe sibling.

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

Usage Guidelines4/5

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

The bulk, all-at-once scope makes the when-to-use context clear, and the confirm guard signals this is a deliberate bulk operation. It never names job_alert_unsubscribe as the alternative for single-alert removal, so the routing guidance is implied rather than explicit.

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.