AI Applyd

Translate Resume

getmattered_translate_resume

Translate the default saved resume-builder document, or the first saved builder document if no default is set, into another language (for example Spanish, French, German, Portuguese or Japanese), ready to send to employers in that market. Returns the new resume's title and a link; the translation is saved as a separate resume and the original stays unchanged. Works from the user's resume on file, or a resume they paste or attach in this chat. Uses the user's AI credits. Do not use it to tailor a resume to a job; use getmattered_optimize_resume, or getmattered_apply, which tailors every application. It also works without a resume-builder document. It uses the resume the user pasted or attached in this conversation (pass its text as resume_text), else the base resume uploaded to their account, else their resume-builder document. In ChatGPT the user can attach a resume file; pass it as resume_file.

Input Schema

Name	Required	Description
`resume_file`	No	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.
`resume_text`	No	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.
`target_language`	Yes	Target language (e.g. "Spanish", "French", "German", "Japanese")

Output Schema

Name	Required	Description
`url`	Yes
`source`	No	pasted / attached: the resume shared in this chat; on_file: the uploaded base resume (ids are document ids); builder: a resume-builder document (ids are builder ids).
`sourceResumeId`	Yes
`targetLanguage`	Yes
`translatedTitle`	Yes
`translatedContent`	No	The translated resume text, when it is ready.
`translatedResumeId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 24, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The description adds important behavior beyond the annotations: the translation is saved as a separate resume, the original stays unchanged, the tool uses the user's AI credits, and it returns a title and link. These details are consistent with the non-read-only, non-destructive, non-idempotent annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The key purpose, output behavior, and alternatives are front-loaded and easy to scan. There is some repetition about resume sources and working without a builder document, but the length is justified by the tool's multiple input paths.

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?

Given the output schema and high schema coverage, the description is complete enough for correct invocation: it covers source selection, file handling, credit usage, output behavior, and when to use a sibling tool instead.

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 parameters are already documented. The description still adds useful meaning by specifying source precedence: pasted/attached resume text first, then the account's base resume, then the resume-builder document, and by clarifying when to pass resume_file.

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?

The description states a specific verb and resource: translating a resume-builder document into another language. It also clarifies the source-document fallback behavior and distinguishes the tool from resume tailoring by naming siblings getmattered_optimize_resume and getmattered_apply.

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 says when not to use this tool (to tailor a resume to a job) and names the alternatives. It also explains when it works without a resume-builder document and gives source precedence for pasted/attached resumes.

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

All AI Applyd tools Inspect

Try in Browser

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.