reminder_listLists tracked jobs that have reminders set, ordered by reminder time (soonest first).
Input:
limit: Number of results to return (default 20, max 50)
Output: Returns a list of tracked jobs with active reminders.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Number of results to return (default 20, max 50) |
| Name | Required | Description | Default |
|---|---|---|---|
| hasMore | No | ||
| totalCount | No | ||
| trackedJobs | No |
Changes observed during successful MCP inspections.
Output schema / properties / trackedJobs / items / properties / appliedAt / typePrevious value: -"string"New value: +[
+ "string",
+ "null"
+]Output schema / properties / trackedJobs / items / properties / createdAt / typePrevious value: -"string"New value: +[
+ "string",
+ "null"
+]Output schema / properties / trackedJobs / items / properties / deadline / typePrevious value: -"string"New value: +[
+ "string",
+ "null"
+]Output schema / properties / trackedJobs / items / properties / notes / typePrevious value: -"string"New value: +[
+ "string",
+ "null"
+]Output schema / properties / trackedJobs / items / properties / reminderAt / typePrevious value: -"string"New value: +[
+ "string",
+ "null"
+]Output schema / properties / trackedJobs / items / properties / salaryOfferedType / typePrevious value: -"string"New value: +[
+ "string",
+ "null"
+]Output schema / properties / trackedJobs / items / properties / subStatus / typePrevious value: -"string"New value: +[
+ "string",
+ "null"
+]Output schema / properties / trackedJobs / items / properties / updatedAt / typePrevious value: -"string"New value: +[
+ "string",
+ "null"
+]Input schema / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema"Input schema / additionalPropertiesAdded value: +falseOutput schema / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema"Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "hasMore": {
+ "type": "boolean"
+ },
+ "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"
+}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 usefully adds the sort order (soonest first) and that only jobs with *active* reminders appear, but says nothing about pagination, total counts, or how to page past the 50-result cap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The lead sentence is front-loaded and earns its place. The Input section duplicates the schema description word-for-word and the Output section restates what the output schema already covers, so roughly a third of the text is redundant padding.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a read-only list with one optional, fully documented parameter and an existing output schema, the description is nearly sufficient — the agent needs no return-value detail. The remaining gap is routing guidance among the many sibling list/search/alert tools.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the single `limit` parameter is fully documented in the schema. The Input block merely restates it verbatim, adding no syntax, ordering, or default behavior beyond what the schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource with scope ("Lists tracked jobs that have reminders set") plus an ordering guarantee (soonest first), which separates it from tracker_list and jobs_search. It stops short of naming a sibling to prefer or avoid, so it is clear but not fully differentiated.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use or when-not-to-use guidance. With siblings like tracker_list and reminder_set/reminder_delete in the same namespace, the description never says which one to pick when an agent wants jobs versus reminders versus alerts.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.