Skip to main content
Glama

Save Localization settings

save_localization
Destructive

PARTIAL SAVE: writes ONLY the 'Localization' field of TitlePublicConfigurationModel; all other v1/v2 fields stay untouched. Localization SETTINGS — which locales the title offers, which one is the default (and therefore the fallback), what to render for a missing key, and the store limits. The translation TABLES are deliberately NOT here: they live in the separate TitleLocalization collection (one document per title+locale) and are delivered one file per locale, because text changes far more often than balance and must not invalidate the whole title config. Client resolution is t(x) = own table -> fallback table -> x itself, which is why a title whose DisplayName fields hold literal names keeps working unchanged: a literal is simply a key with no translation. Add or edit translations through the Localization endpoints, not through this section.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYesLocalization settings of the title. The translation TABLES are not stored here: they live in the separate TitleLocalization collection (one document per title+locale) and are delivered one file per locale. This section only declares which locales exist, which one is the fallback, and the store limits.
title_idYesTitleID, для которого сохраняются данные.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.