GetMattered

Rewrite Application Documents

getmattered_refine_application_documents

Destructive

Rewrites the tailored resume or cover letter of unsent applications from the user's own words. Nothing is sent. Uses AI credits.

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_ids": "<application_ids>",
      "document_type": "<document_type>",
      "instructions": "<instructions>"
    },
    "name": "getmattered_refine_application_documents"
  }
}

Input Schema

Name	Required	Description
`instructions`	Yes	What to change, in the user's own words (up to 2,000 characters).
`document_type`	Yes	"resume" or "cover_letter": which document of each application to rewrite.
`application_ids`	Yes	Application ids to act on, 1 to 25 (e.g. [1550, 1551]), from getmattered_get_applications

Output Schema

Name	Required	Description
`results`	Yes
`decision`	Yes	The operation that ran, one of approve, reject, cancel, refine, re_prepare or set_stage.
`attempted`	Yes
`setupStep`	No	Present while account setup is open: the first setup step.
`succeeded`	Yes
`notConfirmed`	Yes	True when the user declined the confirmation prompt and nothing was sent.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 8, 2026

changedOutput schema / properties / decision / description

Previous value: -"The operation that ran: approve, reject, cancel, refine, re_prepare or set_stage."New value: +"The operation that ran, one of approve, reject, cancel, refine, re_prepare or set_stage."

changedOutput schema / properties / results / items / properties / status / description

Previous value: -"Our own record after the action. Never proof the employer received it."New value: +"Our own record after the action, which is not proof the employer received it."

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."

Changed2 schema fields changedNov 8, 2026

removedOutput schema / properties / confirmToken

Removed value: -{
-  "description": "Approve of one email application only: nothing was sent yet. Show the user the exact email, then pass this as confirm_token with the same application id once they say yes. Works once, for 10 minutes, and only while the email is unchanged.",
-  "type": [
-    "string",
-    "null"
-  ]
-}

changedOutput schema / required

Previous value: -[
-  "decision",
-  "results",
-  "succeeded",
-  "attempted",
-  "notConfirmed",
-  "confirmToken"
-]New value: +[
+  "decision",
+  "results",
+  "succeeded",
+  "attempted",
+  "notConfirmed"
+]

Changed2 schema fields changedNov 8, 2026

addedOutput schema / properties / confirmToken

Added value: +{
+  "description": "Approve of one email application only: nothing was sent yet. Show the user the exact email, then pass this as confirm_token with the same application id once they say yes. Works once, for 10 minutes, and only while the email is unchanged.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "decision",
-  "results",
-  "succeeded",
-  "attempted",
-  "notConfirmed"
-]New value: +[
+  "decision",
+  "results",
+  "succeeded",
+  "attempted",
+  "notConfirmed",
+  "confirmToken"
+]

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"
+}

AddedOct 25, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Adds genuinely useful context beyond the annotations: no submission happens, and AI credits are consumed. However, with destructiveHint=true, the description never says whether the existing tailored document is overwritten or replaced irrevocably, which is the key behavior an agent needs before calling.

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?

Three short sentences, front-loaded with the action and resource, then the two facts an agent most needs (no send, credit cost). No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema is present, so return values need no explanation. Still, for a destructive, non-idempotent rewrite with a 25-application batch limit, the description omits what happens to the prior document version and whether repeated calls stack changes.

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 all three parameters are already documented. The phrase 'from the user's own words' loosely reinforces the instructions parameter but adds no format or constraint detail beyond the schema's 2,000-character note.

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: 'Rewrites the tailored resume or cover letter'. The 'unsent applications' qualifier narrows scope and helps separate it from getmattered_generate_cover_letter and getmattered_optimize_resume, though those siblings are never named outright.

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?

The 'unsent applications' precondition implies when this tool applies, and 'from the user's own words' hints at the instructions-driven workflow. But there is no explicit routing against the many adjacent tools (generate, optimize, score, reprepare) that an agent must choose between.

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.