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

by io.github.foundrole

Overview Discussions Admin

Delete a reminder

reminder_delete

Destructive

Deletes a reminder from a tracked job.

Input:

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

Output: Returns the updated tracked job with reminderAt cleared.

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
`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"

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"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 openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond the annotations: the effect is clearing `reminderAt` on the tracked job rather than removing the job. It does not address what happens if no reminder exists, 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 core sentence is front-loaded and clear, but the Input and Output blocks largely duplicate the input schema's parameter description and the output schema respectively. Those sections dilute rather than sharpen the definition, though the total length remains short.

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?

With one required parameter, full schema coverage, an output schema, and annotations, the definition covers the essentials: what it does, which ID to supply, and the resulting state. The remaining gap is failure behavior (deleting a non-existent reminder) for a mutation flagged as non-idempotent.

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% for the single parameter, so the schema already carries the semantics. The Input section of the description restates the schema text nearly verbatim, adding no syntax, format, or sourcing detail beyond what the schema provides; 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 opens with a specific verb+resource: 'Deletes a reminder from a tracked job,' which clearly separates it from sibling verbs like reminder_set or reminder_list without opening a schema. It does not, however, explicitly name an alternative or contrast itself with them, so it stops short of full sibling differentiation.

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?

There is no explicit when-to-use/when-not-to-use guidance or named alternative (e.g., reminder_set for replacing a reminder). The only guidance is implicit and ID-scoped: the description warns that `tracked_job_id` must come from `tracker_list` output and is distinct from `trackable.id` and `job.id`, which is a partial disambiguation guideline at best.

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.