Skip to main content
Glama

List Due Follow-ups

getmattered_list_due_follow_ups
Read-onlyIdempotent

Lists job applications that are due a follow-up email, ordered by urgency, so you can see which applications need attention without changing any data.

Instructions

Lists job applications due a follow-up email, most urgent first. 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_due_follow_ups"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
draftYesFrom getmattered_draft_follow_up: the drafted message. Nothing was sent.
actionYesThe operation that ran, one of list, history, draft, send or record_sent.
historyYesFrom getmattered_list_sent_follow_ups: follow-ups already sent, newest first.
recordedYesFrom getmattered_send_follow_up or getmattered_record_follow_up: the follow-up count after it was recorded.
followUpsYesFrom getmattered_list_due_follow_ups: applications whose follow-up is due, most urgent first.
setupStepNoPresent while account setup is open: the first setup step.
nextCursorYesFrom getmattered_list_sent_follow_ups: the cursor value for the next page. Null on the last page.
confirmTokenYesFrom 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.
notConfirmedYesTrue when the user declined the confirmation and nothing was sent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.13.2
    • 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."
    • addedOutput schema / properties / setupStep
      Added value: +{
      +  "description": "Present while account setup is open: the first setup step.",
      +  "type": "string"
      +}
  2. Changed2 schema fields changedv1.13.0
    • 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"
      +]
  3. Addedv1.10.2

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so "Changes nothing" largely restates what the annotations provide. The one piece of genuinely additive behavior is the "most urgent first" sort order, which tells the agent the result set is pre-ranked; there is no disclosure of result limits or pagination.

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, zero filler, with the resource and the sort order front-loaded. Every clause carries information an agent can act on.

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?

An output schema exists, so return values need not be described, and the zero-parameter surface keeps the calling contract simple. The remaining gap is the undefined notion of "due" — the exact rule that marks an application as eligible is left implicit.

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?

The tool takes zero parameters, so there is no parameter semantics for the description to explain; baseline is 4. The description correctly implies no filtering knobs are needed because this is a fixed list.

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 job applications due a follow-up email," plus an ordering guarantee ("most urgent first"). It implicitly contrasts with the sent-follow-ups sibling via the word "due," but never names that sibling or states the contrast explicitly.

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 inferable from the phrase "due a follow-up email" — an agent would call this to find which applications need a nudge. However, there is no explicit when-to-use, no mention of the adjacent list_sent_follow_ups alternative, and no statement of what counts as "due" (window, threshold, or stage).

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