AI Applyd

Translate Resume

aiapplyd_translate_resume

Translate your saved resume into another language and keep the original unchanged. Get a new resume ready to send to employers, with the translation saved separately.

Instructions

Translate the user's base resume, the one saved on their AI Applyd account, 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. Needs a resume on file (see aiapplyd_set_resume) and 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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`target_language`	Yes	Target language (e.g. "Spanish", "French", "German", "Japanese")

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`sourceResumeId`	Yes
`targetLanguage`	Yes
`translatedTitle`	Yes
`translatedResumeId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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.7/5.0

Behavior5/5

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

Beyond the annotations, the description explains important side effects and safety-related behavior: the translation is saved as a separate resume, the original stays unchanged, and the operation uses AI credits. It also states what the return value contains (new resume title and link), adding meaningful behavioral context beyond the raw annotations.

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?

The description is informative yet compact, front-loading the core purpose before adding return information, prerequisites, and exclusions. Every sentence earns its place, with no redundant or filler content.

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?

For a single-parameter tool with an output schema and annotations, the description covers the key operational context: prerequisite resume, credit usage, side effects, return value, and when to use a different tool. Nothing essential is missing for an agent to decide whether and how to invoke this tool correctly.

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% and the single parameter target_language is already documented in the schema, so the baseline is 3. The description reinforces the parameter by giving example languages, but does not add substantial new semantics beyond what the schema already provides.

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 names the specific operation (translate the user's saved base resume) and the resource, and clearly distinguishes it from related tools like aiapplyd_optimize_resume and aiapplyd_apply. The purpose is unambiguous, and even the context of where the translation can be sent is included.

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?

The description explicitly states when to use this tool (translating an existing resume for another market) and when not to use it (tailoring a resume to a job), naming the alternatives aiapplyd_optimize_resume and aiapplyd_apply. It also notes the prerequisite of having a resume on file and that the operation consumes AI credits, giving an agent clear selection criteria.

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

Deploy Server