Localize from inside your AI assistant.

readRead the catalog and export files.

• list_projects

  Use this first: it lists the localization projects this connection can access and gives the project slug every other tool takes. Returns each project's slug, name, source locale, target locales and editor URL.

• list_locales

  Use this to learn a project's locale codes before reading or writing translations. Returns every locale with the source locale marked, plus the project's iOS string tables.

• list_keys

  Use this to see a project's whole key set and its naming conventions. Returns every key with its string table, plural flag, tags, description and length limit, but no translations.

• get_translations

  Use this to read one key's stored values in every locale, source locale first. Each value carries its state (untranslated, translated or verified) and, for plural keys, its CLDR category.

• pull_file

  Use this to export one locale as a complete string file (xcstrings, android-xml, json, csv, strings, stringsdict, next-intl), exactly as the CLI writes it to disk. Returns the file's text, which can be large for a big catalog.

• search

  Use this to find string keys by free text when the exact key name is unknown. Matches key names, descriptions and source-language text, case-insensitively, across every project this connection can see. Returns up to 20 results, each with an id, title (the key name), text (its source text) and url (the key in the web editor); pass an id to fetch for the full record.

• fetch

  Use this to read one search result in full. Takes the id a search result returned and returns the key's description, string table, length limit, plural flag, tags, source locale and every translation with its state, as text and as metadata.

• get_coverage

  Use this to answer how much of a project is translated. Returns the total number of translatable keys and, per target locale, how many keys are untranslated, translated (drafted but unreviewed) and verified, with the verified share as a percentage. A plural key counts once and is untranslated until every form the locale needs has text. Call list_missing for the keys behind a number.

• list_missing

  Use this to see what is left to do in one locale: every key that is not yet verified there, with its description, length limit, plural flag, source text, current value and state. Untranslated keys have no usable text yet; translated ones have a draft awaiting review. Pass state to narrow to one of those. Pages of 50 keys by default (at most 200); pass nextCursor back as cursor until it is null. Write the missing values with set_translations.

• list_glossary

  Consult this before translating or writing any value: it returns the project's glossary, the binding term base every translation must follow. A term marked doNotTranslate is kept exactly as written in every locale (brand and product names); a term with a translation must be rendered with that wording, and its note explains when. Pass a locale to get only the terms that bind it (project-wide terms plus that locale's own). Prefer glossary wording over your own whenever a term occurs in the source text.

• check_translations

  Use this before set_translations to validate hand-written values without writing anything. Runs the editor's five checks against the proposed values: placeholders match the source text, the value fits the key's length limit, glossary terms are honoured, the value is consistent with sibling keys sharing the same source text, and the value is not empty. Takes the same values shape as set_translations and returns the issues per locale (check type and message); an empty list means the value would pass.

• list_activity

  Use this to see who changed which translations recently: the 20 latest events by default, newest first, each with the key, locale, whether the value was translated or verified, when, and the actor (a person's name or an API token's name; values written by a token or an assistant are unverified drafts). To page further back, call again with cursor set to the nextCursor of the previous page, and stop when nextCursor is null.

pushWrite values and upload source files.

• set_translations

  Use this to write one key's value in one or more locales; the key must already exist. A plural key takes an object of the locale's CLDR categories instead of a string. Written values are stored as unverified drafts until a person verifies them in the editor, and writing the source locale demotes verified targets. Returns the cells written.

• push_file

  Use this to upload a whole string file and upsert every key in it, creating keys that do not exist yet. Additive: keys missing from the file are left in place. Without a locale the file is taken as the source locale. Returns counts of keys created and updated.

• draft_translations

  Use this to have the product's own AI draft one key's translations, using the project's glossary, translation memory and the key's length limit. Without locales it drafts every target locale still missing a value; named locales are redrafted unless verified (verified values are never replaced). Drafts are written as unverified, AI-marked values a person must verify in the editor. Returns what was drafted per locale and which locales were skipped and why. Spends model calls, so pass at most 20 locales and do not call it in a loop.

manageCreate, edit and delete keys.

• create_key

  Use this to add one new key with its metadata: a description for translators, a length limit, the plural flag, its iOS string table and tags. Fails if the name already exists. Returns the new key's id and name; it has no values until translations are set.

• update_key

  Use this to change an existing key's metadata. Omitted fields keep their value. tags replaces the whole set and cannot be combined with addTags or removeTags. Returns the key's id and name.

• delete_keydestructive

  Use this only when the user has explicitly asked to delete this key: it removes the key and every translation of it, permanently. Returns the deleted key's name.

• add_glossary_term

  Use this to record a term every later translation must respect: either a do-not-translate rule (doNotTranslate true, no translation needed) or a required wording (translation set). Without a locale the term binds every locale of the project; with one it is that locale's preferred wording. Fails with a conflict if the term already exists in that scope. Returns the new term's id. Adding a term changes future translations and the terminology check, never stored values.

• delete_glossary_termdestructive

  Use this only when the user has explicitly asked to remove a glossary term: later translations stop being bound by it, permanently. Takes the term's id or its source term; a source term that exists in several scopes needs a locale (or the id) to pick one. Returns the deleted term.