Skip to main content
Glama

Optimize Resume

getmattered_optimize_resume

Tailor a resume to a target job description for ATS screening or improve it generally without changing the original resume; AI credits are used.

Instructions

Tailors a resume to a job description for ATS screening, or improves it in general. The base resume does not change. Uses AI credits.

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

Input Schema

NameRequiredDescriptionDefault
resume_fileNoA resume file the user attached in ChatGPT, as the file itself. GetMattered reads it once: PDF, DOCX or plain text, up to 10 MB.
resume_textNoFull text of the resume to optimize. The resume the user pasted or attached in this conversation, as plain text. Left out, the resume already on the user's GetMattered account is used.
job_descriptionNoFull text of the target job description (optional; without it, the optimization is general)

Output Schema

NameRequiredDescriptionDefault
changesYes
setupStepNoPresent while account setup is open: the first setup step.
optimizedResumeYes
projectedAtsScoreYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.13.2
    • changedInput schema / properties / job_description / description
      Previous value: -"Full text of the target job description (optional, omit for general ATS optimization)"New value: +"Full text of the target job description (optional; without it, the optimization is general)"
    • changedInput schema / properties / resume_file / description
      Previous value: -"In ChatGPT the user can attach a resume file; pass it as resume_file. It is downloaded once, right away: PDF, DOCX or plain text, up to 10 MB."New value: +"A resume file the user attached in ChatGPT, as the file itself. GetMattered reads it once: PDF, DOCX or plain text, up to 10 MB."
    • changedInput schema / properties / resume_text / description
      Previous value: -"Full text of the resume to optimize. The resume the user pasted or attached in this conversation, as plain text. Omit it to use the resume already on the user's GetMattered account."New value: +"Full text of the resume to optimize. The resume the user pasted or attached in this conversation, as plain text. Left out, the resume already on the user's GetMattered account is used."
    • addedOutput schema / properties / setupStep
      Added value: +{
      +  "description": "Present while account setup is open: the first setup step.",
      +  "type": "string"
      +}
  2. Addedv1.9.1

TDQS

A3.8/5.0
Behavior4/5

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

Goes meaningfully beyond the annotations by disclosing that the stored base resume is left intact and that the call consumes AI credits — a real cost signal the annotations do not carry. Given destructiveHint=false is already declared, the 'base resume does not change' line reinforces rather than merely repeats, and the credit disclosure is genuinely additive. It still doesn't say whether the tailored result is persisted as a new resume or only returned.

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: purpose, a key behavioral guarantee, and a cost note — all front-loaded with zero filler. Every sentence earns its place.

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 no explanation, and the annotations cover the safety profile. The description supplies the non-obvious facts (base resume untouched, credits consumed). Minor gap: no statement about whether the optimized resume is saved to the account, which matters for a downstream apply flow.

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 file format/size limits, the 50,000-character bound, and the account-resume fallback are already documented. The description adds nothing about parameter syntax or precedence (e.g. what happens if both resume_file and resume_text are supplied). Baseline 3 applies when the schema carries the load.

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 concrete verb and resource ('tailors a resume') plus the two modes it supports (ATS-tailoring against a job description, or general improvement). An agent can tell what it produces. It stops short of naming the sibling it is not — e.g. getmattered_score_resume or getmattered_create_resume_draft — so differentiation relies on inference.

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 'or improves it in general' clause signals a second use case, but there is no explicit when-to-use / when-not-to-use guidance and no routing to adjacent tools (score vs. draft vs. refine). The agent must guess whether this is the right step before scoring or applying.

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