Skip to main content
Glama

Edit a locale draft

optimizer_edit_locale
Idempotent

Edit draft listing fields for a single locale, such as title, keywords, or description; an empty string clears a field. Your edits persist when the listing is localized again.

Instructions

Change fields of one locale's draft listing (empty string clears a field). Edited fields are kept when the listing is localized again (unless optimizer_localize gets redoEdited).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>",
      "locale": "<locale>",
      "fields": "<fields>"
    },
    "name": "optimizer_edit_locale"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsYesFields to change; an empty string clears the field.
localeYesLocale of the draft.
projectIdYesProject id (from get_overview).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.7

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: an empty string clears a field, and edits survive re-localization unless optimizer_localize is called with redoEdited — lifecycle context an agent could not infer.

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?

Two compact sentences; the core action comes first and the persistence caveat follows. No filler, and the parenthetical is the most efficient way to convey the clear-field rule.

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?

For a three-parameter, fully documented edit tool with annotations covering safety and idempotency, the definition gives an agent what it needs to call correctly. Return behavior is unstated, but with no output schema that is a minor gap rather than a blocking one.

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 description coverage is 100%, including per-field char limits and the empty-string-clears rule, so the schema carries the semantics. The description restates the clearing behavior rather than adding new detail beyond it, making the baseline of 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Change fields of one locale's draft listing', scoped to a single locale's draft rather than the project as a whole. It does not explicitly route against siblings such as optimizer_localize or edit_keyword, but the parenthetical about clearing fields sharpens the operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 'draft listing' and the note about re-localization, which tells an agent this edits pre-publish content. There is no explicit when-not guidance, though the mention of optimizer_localize with redoEdited hints at the interplay between the two tools.

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

Deploy Server

Other Tools