Skip to main content
Glama

translate_prompts

Read-only

AI drafts of a project's tracked prompts in another market's language, the first step of adding a market: each prompt rephrased the way people in the new market ask it, with brand and product names kept as written. Read-only: nothing is saved; the drafts are meant for review, and the final texts go to add_market as prompts. It spends AI (one or two model calls on the workspace's own key or Managed AI) and counts toward the workspace's 20 assistant-started scans, briefs and suggestions a day.

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": {
      "toMarket": "<toMarket>"
    },
    "name": "translate_prompts"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientIdNoClient id — uses the AI-Visibility project its Overview opens in the app (the newest).
toMarketYesThe new market as a locale: "es-ES", "en-US", or a language alone such as "es".
projectIdNoAI-Visibility project id.
promptIdsNoOnly these prompts (ids from list_prompts). Default: every active prompt of fromMarket, at most 200.
fromMarketNoThe market whose active prompts are translated, as a locale. Default: the project's own market.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly/non-destructive, but the description adds substantial beyond-schema context: nothing is saved, drafts are for review only, it spends AI (one or two model calls on the workspace's own key or Managed AI), and it consumes a slot from the workspace's 20 daily assistant-started actions. This is exactly the cost/quota disclosure an agent needs.

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?

Purpose is front-loaded in the first clause, followed by behavioral caveats in order of importance (read-only, then AI cost/quota). Three dense sentences with no wasted words.

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?

Despite no output schema, the description explains what the return is (reviewable drafts destined for add_market), the read-only nature, and the cost/quota implications. Nothing critical for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so parameters are documented structurally; the description adds useful semantic framing by clarifying that the produced drafts become the `prompts` value for add_market, which helps the agent understand what the output feeds into. It does not add per-parameter syntax detail beyond the schema, keeping it slightly under a 5.

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?

States a specific action (rephrasing a project's tracked prompts into another market's language) with a clear scope constraint (brand and product names kept as written). It is easily distinguishable from add_market and suggest_prompts, naming add_market as the downstream step.

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?

Explicitly frames this as 'the first step of adding a market' and states the drafts are 'meant for review, and the final texts go to add_market as prompts.' That gives the agent both the when-to-use condition and the correct follow-up tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources