Skip to main content
Glama

Reply to an Employer Email

getmattered_reply_to_email
Destructive

Sends an approved plain-text reply to a recruiter or employer email under your name, using a message ID from your inbox. Returns a confirmation token first when the client lacks a confirmation form.

Instructions

Sends the user's reply to one recruiter or employer email, under the user's name, from their GetMattered address (or their connected mailbox, when the thread arrived there). message_id comes from getmattered_get_inbox, which also drafts replies. 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 reply 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": {
      "message_id": "<message_id>",
      "body": "<body>"
    },
    "name": "getmattered_reply_to_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesThe exact plain-text reply the user approved, signed with their name.
message_idYesThe message_id of the email to answer, from getmattered_get_inbox. The reply goes to the newest email the employer sent in that conversation.
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.

Output Schema

NameRequiredDescriptionDefault
sentAtYes
statusYessent: the email went out; not_confirmed: the user declined, nothing was sent; confirmation_required: nothing was sent yet, and the email goes out with confirmToken after the user's yes.
toEmailYes
messageIdYesThe email that was answered.
setupStepNoPresent while account setup is open: the first setup step.
fromAddressYes
confirmTokenYesWith confirmation_required: the confirm_token value that sends this reply, with the same message_id and body, after the user's yes. Works once, for 10 minutes.
sentMessageIdYesThe sent reply in the inbox. Null when 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 exact plain-text reply the user approved, signed with their name. Up to 50,000 characters."New value: +"The exact plain-text reply the user approved, signed with their name."
    • 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. Changed4 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."
    • changedOutput schema / properties / confirmToken / description
      Previous value: -"With confirmation_required: pass as confirm_token, with the same message_id and body, once the user says yes. Works once, for 10 minutes."New value: +"With confirmation_required: the confirm_token value that sends this reply, with the same message_id and body, after the user's yes. Works once, for 10 minutes."
    • addedOutput schema / properties / setupStep
      Added value: +{
      +  "description": "Present while account setup is open: the first setup step.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / status / description
      Previous value: -"sent: the email went out; not_confirmed: the user declined, nothing was sent; confirmation_required: nothing was sent yet, show the user the email and send it with confirmToken after their yes."New value: +"sent: the email went out; not_confirmed: the user declined, nothing was sent; confirmation_required: nothing was sent yet, and the email goes out with confirmToken after the user's yes."
  3. Changed5 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": "With confirmation_required: pass as confirm_token, with the same message_id and body, once the user says yes. Works once, for 10 minutes.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • changedOutput schema / properties / status / description
      Previous value: -"sent: the email went out; not_confirmed: the user declined, nothing was sent."New value: +"sent: the email went out; not_confirmed: the user declined, nothing was sent; confirmation_required: nothing was sent yet, show the user the email and send it with confirmToken after their yes."
    • changedOutput schema / properties / status / enum
      Previous value: -[
      -  "sent",
      -  "not_confirmed"
      -]New value: +[
      +  "sent",
      +  "not_confirmed",
      +  "confirmation_required"
      +]
    • changedOutput schema / required
      Previous value: -[
      -  "status",
      -  "messageId",
      -  "sentMessageId",
      -  "toEmail",
      -  "fromAddress",
      -  "sentAt"
      -]New value: +[
      +  "status",
      +  "messageId",
      +  "sentMessageId",
      +  "toEmail",
      +  "fromAddress",
      +  "sentAt",
      +  "confirmToken"
      +]
  4. Addedv1.9.1

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the two-step confirm_token handshake, the condition when no confirmation form exists in the client, the 10-minute single-use nature of the token (in schema), and that a sent reply is irreversible. This directly contextualizes destructiveHint=true and idempotentHint=false rather than repeating them.

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?

Four sentences, each carrying distinct load: what it does, where the id comes from, how confirmation works, and the irreversibility warning. The scope and the critical caveat are front-loaded 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?

For a destructive, non-idempotent outbound send with an output schema present, the description covers identity of sender, source of the id, the confirmation protocol, and irreversibility. An agent has everything needed to call it correctly and safely.

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 coverage is 100%, so the schema already documents all three parameters including confirm_token lifetime and body constraints. The description adds only the provenance of message_id (from getmattered_get_inbox) and sender identity, which largely restates the schema's own wording.

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?

States a specific verb+resource: sends the user's reply to one recruiter or employer email, under the user's name from their GetMattered address or connected mailbox. It also distinguishes itself from getmattered_get_inbox, which reads the inbox and drafts replies rather than sending them.

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

Usage Guidelines4/5

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

Gives clear routing context: message_id comes from getmattered_get_inbox, which also drafts replies, so an agent knows to draft there and send here. It explains the confirmation flow but does not state explicit negative cases (e.g. not for starting new threads or for follow-ups, which have their own send_follow_up sibling).

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