AI Applyd

Translate Resume

aiapplyd_translate_resume

Instructions

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 aiapplyd_optimize_resume, or aiapplyd_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

TableJSON 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 AI Applyd account.
`target_language`	Yes	Target language (e.g. "Spanish", "French", "German", "Japanese")

Output Schema

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

Changed5 schema fields changedv1.9.0Oct 14, 2026

addedInput schema / properties / resume_file

Added value: +{
+  "additionalProperties": false,
+  "description": "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.",
+  "properties": {
+    "download_url": {
+      "format": "uri",
+      "type": "string"
+    },
+    "file_id": {
+      "type": "string"
+    },
+    "file_name": {
+      "type": "string"
+    },
+    "mime_type": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "download_url",
+    "file_id"
+  ],
+  "type": "object"
+}

addedInput schema / properties / resume_text

Added value: +{
+  "description": "The resume the user pasted or attached in this conversation, as plain text. Omit it to use the resume already on the user's AI Applyd account.",
+  "maxLength": 50000,
+  "minLength": 50,
+  "type": "string"
+}

addedOutput schema / properties / source

Added value: +{
+  "description": "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).",
+  "enum": [
+    "pasted",
+    "attached",
+    "on_file",
+    "builder"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / sourceResumeId / type

Previous value: -"number"New value: +[
+  "number",
+  "null"
+]

addedOutput schema / properties / translatedContent

Added value: +{
+  "description": "The translated resume text, when it is ready.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed2 schema fields changedv1.8.0Sep 25, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "sourceResumeId": {
+      "type": "number"
+    },
+    "targetLanguage": {
+      "type": "string"
+    },
+    "translatedResumeId": {
+      "type": "number"
+    },
+    "translatedTitle": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "targetLanguage",
+    "sourceResumeId",
+    "translatedResumeId",
+    "translatedTitle",
+    "url"
+  ],
+  "type": "object"
+}

First observedv1.3.0Sep 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false; the description adds real context beyond them: the translation is saved as a separate resume with the original unchanged, it consumes AI credits, and the attached file is downloaded once immediately (10 MB, PDF/DOCX/text). It does not mention rate limits or how credits are consumed, so it stops short of full disclosure.

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

Conciseness3/5

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

The purpose and prohibition are well front-loaded, but the source-resolution logic is restated three times across the paragraph ('Works from the user's resume on file, or a resume they paste or attach...' / 'It also works without a resume-builder document...' / 'It uses the resume the user pasted or attached...'), and language examples are duplicated. It meanders where two tight sentences would do.

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 the return values need not be explained, yet the description still covers them briefly. Across a 1-required-param tool with a nested resume_file object, it covers sources, language, credits, non-destructiveness, and alternatives — only the credit-consumption mechanics are left open.

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 description coverage is 100%, so the baseline is 3. The description nonetheless adds routing semantics the schema cannot: pass pasted/attached conversation text as resume_text, pass a ChatGPT attachment as resume_file, and omit resume_text to fall back to the account resume. That precedence logic is genuinely useful beyond the field descriptions.

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?

States a specific verb (translate) and resource (resume), plus the exact scope of which document is translated (the default saved resume-builder document, or the first saved one if no default). It also names the sibling tools it is not (aiapplyd_optimize_resume, aiapplyd_apply) with the reason, so an agent can distinguish it without opening another schema.

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?

Explicitly says when not to use it ('Do not use it to tailor a resume to a job; use aiapplyd_optimize_resume, or aiapplyd_apply') and enumerates the source-resolution order (pasted/attached text, then account base resume, then resume-builder document). The alternative is named with the selecting condition, leaving little to inference.

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