create_key_with_translations
:
Instructions
Create a new translation key and set translations for multiple languages in a single operation. Accepts language codes (e.g., 'en', 'de', 'fr') instead of language IDs — the tool resolves codes to IDs internally by fetching the project's configured languages. If the key is created but any translation fails, the key is automatically rolled back (deleted). This combines create_key + multiple set_translation calls into one atomic-like operation.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| project_id | Yes | The Texterify project UUID. You can find this value in the project's texterify.json file under the 'project_id' field | |
| name | Yes | The key name used as the i18n identifier in source code, typically in snake_case or dot.notation (e.g., 'welcome_message', 'auth.login.title'). Must be unique within the project | |
| description | No | Optional human-readable description to help translators understand the context (e.g., 'Greeting shown on the homepage header'). This is not the translation — it's metadata about where/how the key is used | |
| html_enabled | No | Set to true if translation values for this key contain HTML markup. When enabled, the Texterify UI shows a rich text editor for translators. Defaults to false | |
| pluralization_enabled | No | Set to true if this key needs plural forms (e.g., '1 item' vs '5 items'). Follows CLDR Plural Rules with forms: zero, one, two, few, many, and other (the content field). Defaults to false | |
| translations | Yes | Array of translations to set for the new key. Each entry specifies a language_code and the translated content. The tool resolves language codes to IDs internally by fetching the project's configured languages |