GetMattered

List Sent Follow-ups

getmattered_list_sent_follow_ups

Read-onlyIdempotent

Lists follow-ups already sent or recorded. Changes nothing.

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": "getmattered_list_sent_follow_ups"
  }
}

Input Schema

Name	Required	Description	Default
`cursor`	No	The nextCursor from the previous page. Left out, the newest page comes back.

Output Schema

Name	Required	Description
`draft`	Yes	From getmattered_draft_follow_up: the drafted message. Nothing was sent.
`action`	Yes	The operation that ran, one of list, history, draft, send or record_sent.
`history`	Yes	From getmattered_list_sent_follow_ups: follow-ups already sent, newest first.
`recorded`	Yes	From getmattered_send_follow_up or getmattered_record_follow_up: the follow-up count after it was recorded.
`followUps`	Yes	From getmattered_list_due_follow_ups: applications whose follow-up is due, most urgent first.
`setupStep`	No	Present while account setup is open: the first setup step.
`nextCursor`	Yes	From getmattered_list_sent_follow_ups: the cursor value for the next page. Null on the last page.
`confirmToken`	Yes	From getmattered_send_follow_up when nothing was sent yet: the confirm_token value that sends this email, with the same arguments, after the user's yes. Works once, for 10 minutes.
`notConfirmed`	Yes	True when the user declined the confirmation and nothing was sent.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 8, 2026

changedOutput schema / properties / action / description

Previous value: -"The operation that ran: list, history, draft, send or record_sent."New value: +"The operation that ran, one of list, history, draft, send or record_sent."

changedOutput schema / properties / confirmToken / description

Previous value: -"From getmattered_send_follow_up when nothing was sent yet: show the user the email, then pass this as confirm_token with the same arguments after their yes. Works once, for 10 minutes."New value: +"From getmattered_send_follow_up when nothing was sent yet: the confirm_token value that sends this email, with the same arguments, after the user's yes. Works once, for 10 minutes."

changedOutput schema / properties / followUps / anyOf

Previous value: -[
-  {
-    "items": {
-      "additionalProperties": false,
-      "properties": {
-        "applicationId": {
-          "description": "Pass as application_id to getmattered_draft_follow_up, getmattered_send_follow_up or getmattered_record_follow_up.",
-          "type": "number"
-        },
-        "company": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "followUpCount": {
-          "type": "number"
-        },
-        "jobTitle": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "lastFollowUpAt": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "nextFollowUpDueAt": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "urgency": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "applicationId",
-        "jobTitle",
-        "company",
-        "urgency",
-        "followUpCount",
-        "lastFollowUpAt",
-        "nextFollowUpDueAt"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "additionalProperties": false,
+      "properties": {
+        "applicationId": {
+          "description": "The application_id getmattered_draft_follow_up, getmattered_send_follow_up and getmattered_record_follow_up take.",
+          "type": "number"
+        },
+        "company": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "followUpCount": {
+          "type": "number"
+        },
+        "jobTitle": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "lastFollowUpAt": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "nextFollowUpDueAt": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "urgency": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "applicationId",
+        "jobTitle",
+        "company",
+        "urgency",
+        "followUpCount",
+        "lastFollowUpAt",
+        "nextFollowUpDueAt"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / nextCursor / description

Previous value: -"From getmattered_list_sent_follow_ups: pass as cursor for the next page. Null on the last page."New value: +"From getmattered_list_sent_follow_ups: the cursor value for the next page. Null on the last page."

changedOutput schema / properties / setupStep / description

Previous value: -"Set while account setup is open: the step to take first."New value: +"Present while account setup is open: the first setup step."

Changed1 schema field changedNov 8, 2026

changedInput schema / properties / cursor / description

Previous value: -"The nextCursor from the previous page. Omit it for the newest."New value: +"The nextCursor from the previous page. Left out, the newest page comes back."

Changed1 schema field changedNov 6, 2026

addedOutput schema / properties / setupStep

Added value: +{
+  "description": "Set while account setup is open: the step to take first.",
+  "type": "string"
+}

Changed2 schema fields changedOct 31, 2026

addedOutput schema / properties / confirmToken

Added value: +{
+  "description": "From getmattered_send_follow_up when nothing was sent yet: show the user the email, then pass this as confirm_token with the same arguments after their yes. Works once, for 10 minutes.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "action",
-  "followUps",
-  "history",
-  "nextCursor",
-  "draft",
-  "recorded",
-  "notConfirmed"
-]New value: +[
+  "action",
+  "followUps",
+  "history",
+  "nextCursor",
+  "draft",
+  "recorded",
+  "notConfirmed",
+  "confirmToken"
+]

AddedOct 25, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and closed-world scope, so the safety profile is fully covered by structured data. 'Changes nothing' is a restatement of readOnlyHint rather than new information, and the description adds nothing about ordering, recency, or volume of returned results beyond what the schema's cursor description supplies.

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?

Two short sentences with zero filler: the action and scope come first, followed by the safety clarification. Nothing is padded or repeated.

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?

Against a single-parameter read tool with rich annotations and an output schema, the description covers what it does and that it is side-effect free. The only meaningful gap is sibling differentiation against getmattered_list_due_follow_ups and getmattered_record_follow_up, which the description leaves to inference.

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?

Only one optional parameter exists and its schema description is complete at 100% coverage, explaining that the newest page is returned when cursor is omitted. The description adds no meaning beyond the schema, which is the expected baseline here.

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?

States a specific verb and resource: 'Lists follow-ups already sent or recorded.' The qualifier 'already sent or recorded' distinguishes it in substance from a due/upcoming list, but it never names the nearby sibling getmattered_list_due_follow_ups, so an agent must infer the boundary itself.

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 phrase 'already sent or recorded' — the agent can guess this is a historical log rather than a to-do list, but there is no explicit when-to-use statement, no mention of the due-follow-ups alternative, and no prerequisite (e.g., account scoping) guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All GetMattered 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.