Skip to main content
Glama

Adapt a post for another market

localize_post
Read-only

Use this when the user wants a post they wrote adapted for readers in another country or language, such as "adapt this for a Japanese audience". Pass the post text, the target market and optionally a platform to check the result against. Returns the adapted text, its language, a short list of what changed and why, and the platform check when one was asked for. It adapts tone, idioms, examples and formats rather than translating word for word, and adds no new claims. Only for the user's own text; it does not publish.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "Our app is a home run for busy parents.",
      "target_market": "Japan"
    },
    "name": "localize_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesYour own post to adapt. Do not paste other people's posts.
platformNoOptional. Checks the adapted text against this platform's length and hashtag rules.
target_marketYesThe audience, such as "Japan", "Brazil", "German-speaking Switzerland" or "Spanish speakers in Mexico".

Output Schema

NameRequiredDescriptionDefault
as_ofYes
checkYes
noticeYes
sourceYes
statusYes
messageNo
languageYes
adaptationsYes
rules_as_ofYes
target_marketYes
localized_textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "target_market": "Japan",
      +    "text": "Our app is a home run for busy parents."
      +  }
      +]
  2. Changed1 schema field changed
    • removedOutput schema / properties / note_from_openkrill
      Removed value: -{
      -  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
      -  "type": "string"
      -}
  3. Changed1 schema field changed
    • addedOutput schema / properties / note_from_openkrill
      Added value: +{
      +  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
      +  "type": "string"
      +}
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Goes beyond the readOnly/destructive annotations by describing the adaptation contract ('adds no new claims', adapts rather than translates) and confirms it never publishes. The openWorldHint and non-idempotent behavior (results may vary between calls) are not surfaced, which is the remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the trigger, then parameters, then return shape, then constraints — a logical order with little waste. The return-value sentence is slightly long for a tool that already has an output schema.

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?

An agent knows when to call it, what to pass, what comes back, and what the tool will and won't do. The 3000-character input limit and the non-determinism hinted by idempotentHint=false are not mentioned, but with an output schema present nothing critical is missing.

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 coverage is 100%, so the description is only restating the parameters ('post text, target market and optionally a platform to check the result against'). It correctly conveys that platform is optional and validation-oriented, but adds no syntax or format detail beyond the schema — baseline 3.

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 verb and resource (adapt a post for another market) plus the exact transformation it performs: tone, idioms, examples and formats rather than word-for-word translation. That distinguishes it clearly from the drafting siblings (draft_posts, draft_video_script) which produce new content rather than reworking the user's own.

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

Usage Guidelines4/5

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

Names a concrete trigger ('the user wants a post they wrote adapted for readers in another country or language') with an example utterance, and carves out an exclusion ('Only for the user's own text; it does not publish'). It does not name a specific alternative sibling or say what to do when the request is actually a translation or a new draft, so it falls short of a 5.

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.