Skip to main content
Glama

Send a Follow-up Email

getmattered_send_follow_up
Destructive

Sends one follow-up email about a job application from the user's connected Gmail or Outlook, within the employer's existing thread, then records it. Only the employer address on file is accepted.

Instructions

Sends one follow-up email about an application, under the user's name, from their connected Gmail or Outlook, in the employer's own thread, and records it. The to address is the employer address on file; any other is refused. getmattered_draft_follow_up writes the text. Without a confirmation form in the client, the first call sends nothing and returns a confirm_token; a second call with that token sends. A sent email cannot be unsent.

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": {
      "application_id": "<application_id>",
      "to": "<to>",
      "subject": "<subject>",
      "body": "<body>"
    },
    "name": "getmattered_send_follow_up"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesThe recipient's email address, exactly as the user gave it.
bodyYesThe exact message text the user approved.
subjectYesThe subject line the user approved.
confirm_tokenNoThe confirm_token of an earlier call that returned confirmation_required, sent after the user said yes to that exact email, with the same arguments. It works once, for 10 minutes.
application_idYesThe application, from getmattered_list_due_follow_ups or getmattered_get_applications.

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. Changed2 schema fields changedv1.20.1
    • changedInput schema / properties / body / description
      Previous value: -"The message text, 20 to 4,000 characters: the exact text the user approved."New value: +"The exact message text the user approved."
    • changedInput schema / properties / confirm_token / description
      Previous value: -"The token from a previous call that returned confirmation_required, valid once the user said yes to that exact email, with the same arguments. It works once, for 10 minutes."New value: +"The confirm_token of an earlier call that returned confirmation_required, sent after the user said yes to that exact email, with the same arguments. It works once, for 10 minutes."
  2. Changed7 schema fields changedv1.13.2
    • changedInput schema / properties / confirm_token / description
      Previous value: -"The token from a previous call that returned confirmation_required. Pass it only after the user said yes to that exact email, with the same arguments. It works once, for 10 minutes."New value: +"The token from a previous call that returned confirmation_required, valid once the user said yes to that exact email, with the same arguments. It works once, for 10 minutes."
    • changedInput schema / properties / to / description
      Previous value: -"The recipient's email address, exactly as the user gave it. Never guess one."New value: +"The recipient's email address, exactly as the user gave it."
    • 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"
      +}
  3. Changed3 schema fields changedv1.13.0
    • addedInput schema / properties / confirm_token
      Added value: +{
      +  "description": "The token from a previous call that returned confirmation_required. Pass it only after the user said yes to that exact email, with the same arguments. It works once, for 10 minutes.",
      +  "format": "uuid",
      +  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
      +  "type": "string"
      +}
    • 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"
      +]
  4. Addedv1.10.2

TDQS

A4.9/5.0
Behavior5/5

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

Beyond annotations (destructiveHint=true, openWorldHint=true, idempotentHint=false), it discloses the external side effects in concrete terms: sent under the user's name, from their connected mailbox, inside the employer's existing thread, and recorded afterwards. It also warns "A sent email cannot be unsent," matching the destructive/non-idempotent annotations rather than contradicting them, and explains the token-gated send path so the agent understands a first call is a no-op.

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?

Five short sentences, each carrying distinct information: purpose, address constraint, drafting alternative, confirmation flow, irreversibility. The most consequential facts (what it does, what cannot be undone) are front-loaded and last-emphasized respectively, with no 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?

An output schema exists so return values need not be described, yet the description still flags the confirm_token response shape, which is the one return behavior an agent must act on. For a destructive, open-world, non-idempotent tool with 5 parameters, the coverage of permissions, prerequisites, and irreversibility leaves nothing material missing.

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%, so the baseline is 3; the description earns a bump by adding a constraint absent from the schema: the recipient must equal the employer address on file or the call is refused. The confirm_token retry semantics (second call with same arguments, valid once for 10 minutes) reinforce rather than merely repeat the schema text.

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?

"Sends one follow-up email about an application" gives a specific verb, resource and cardinality, then narrows the mechanism (under the user's name, from connected Gmail/Outlook, in the employer's own thread) so it is distinguishable from a generic send. It also names the sibling that handles text authoring, getmattered_draft_follow_up, so an agent can route without opening either schema.

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

Usage Guidelines5/5

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

It explicitly routes drafting to getmattered_draft_follow_up and states the hard selection constraint that the "to" address must be the employer address on file, with anything else refused. The two-step confirmation condition (first call returns confirm_token when no confirmation form exists) is spelled out as when/when-not guidance rather than left to inference.

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