Skip to main content
Glama

Translate Resume

getmattered_translate_resume

Translates a resume into a chosen language and saves it as a separate document while preserving the original, using AI credits.

Instructions

Translates a resume into another language and saves it as a separate document. The original stays. Uses AI credits. It reads resume_text first, then the base resume on the account, then the resume-builder document.

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": {
      "target_language": "<target_language>"
    },
    "name": "getmattered_translate_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_textNoThe 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.
target_languageYesTarget language (e.g. "Spanish", "French", "German", "Japanese")

Output Schema

NameRequiredDescriptionDefault
urlYes
sourceNopasted / 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).
setupStepNoPresent while account setup is open: the first setup step.
sourceResumeIdYes
targetLanguageYes
translatedTitleYes
translatedContentNoThe translated resume text, when it is ready.
translatedResumeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.13.2
    • 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: -"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: +"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.7/5.0
Behavior4/5

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

Beyond the annotations the description discloses three real behavioral facts: a new document is created rather than the source being mutated, the original is preserved, and the call consumes AI credits. The stated read order ('resume_text first, then the base resume on the account, then the resume-builder document') is a concrete precedence rule an agent cannot infer from the 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?

Four short sentences, front-loaded with the action and its result, with no filler. The clipped phrasing ('The original stays.', 'Uses AI credits.') is terse rather than padded, so nothing needs removing.

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 and the annotations cover the safety profile, so the description only needs to add cost, source resolution, and non-destructiveness — which it does. Minor omissions remain, such as where the new document lands or whether the source document is named, but nothing blocks correct invocation.

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%, so the parameter meanings are already documented and the baseline is 3. The description adds modest value by spelling out the three-level fallback chain for the resume source, which the schema only summarizes as 'the resume already on the user's account'.

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?

The description names a specific verb and resource ('Translates a resume into another language') and states the resulting artifact ('saves it as a separate document'). It is unambiguous about what the tool produces, though it never differentiates itself from nearby siblings like generate_cover_letter or refine_application_documents.

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?

Usage is implied by the purpose (translate an existing resume), and the note that the original stays gives a useful context cue, but there is no explicit when-to-use / when-not-to-use guidance and no named alternative for adjacent tasks such as rewriting or optimizing a resume.

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