Skip to main content
Glama

Rewrite Application Documents

getmattered_refine_application_documents
Destructive

Rewrite tailored resumes or cover letters for unsent applications using your own instructions, with no applications sent.

Instructions

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

NameRequiredDescriptionDefault
instructionsYesWhat to change, in the user's own words.
document_typeYes"resume" or "cover_letter": which document of each application to rewrite.
application_idsYesApplication ids to act on, 1 to 25 (e.g. [1550, 1551]), from getmattered_get_applications

Output Schema

NameRequiredDescriptionDefault
resultsYes
decisionYesThe operation that ran, one of approve, reject, cancel, refine, re_prepare or set_stage.
attemptedYes
setupStepNoPresent while account setup is open: the first setup step.
succeededYes
notConfirmedYesTrue when the user declined the confirmation prompt and nothing was sent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.20.1
    • changedInput schema / properties / instructions / description
      Previous value: -"What to change, in the user's own words (up to 2,000 characters)."New value: +"What to change, in the user's own words."
  2. Changed3 schema fields changedv1.13.2
    • 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."
    • addedOutput schema / properties / setupStep
      Added value: +{
      +  "description": "Present while account setup is open: the first setup step.",
      +  "type": "string"
      +}
  3. Addedv1.10.2

TDQS

A3.8/5.0
Behavior4/5

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

Adds real context beyond the annotations: "Uses AI credits" is a cost warning, and "Nothing is sent" reassures on external side effects even though destructiveHint=true. It does not explain what happens to the prior document version (overwritten, recoverable, versioned), which is the main behavioral question for a destructive rewrite, keeping it from a 5.

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 verb and scope, then the no-send guarantee, then the credit cost. No filler or redundancy.

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?

Covers the essentials for a destructive, credit-consuming rewrite, and an output schema exists so return values need no explanation. The remaining gap is what happens to the original document content after the rewrite, which is worth stating for a tool annotated destructiveHint=true.

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 description coverage is 100%, with instructions, document_type enum, and the 1-25 application_ids range all documented in the schema. The description only echoes the "user's own words" framing for instructions and adds no new syntax, ordering, or batching semantics, so the baseline 3 applies.

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?

Names a specific verb ("Rewrites") and resource ("the tailored resume or cover letter") and scopes it to "unsent applications," which an agent can use to distinguish it from generate_cover_letter or create_resume_draft. It stops short of naming the sibling to use for new documents, so the line is drawn by state rather than by alternative.

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" qualifier implicitly tells the agent when this applies and excludes already-sent ones, and "Nothing is sent" reinforces that this is not a dispatch step. However, it never states what to do when an application has already been sent, nor which sibling to use to create a new document rather than rewrite one.

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