Skip to main content
Glama
ShipLocale

shiplocale-mcp

Official
by ShipLocale

AI-improve copy (returns text, saves nothing)

improve_copy

Rewrites app store copy by applying an action (e.g., improve, shorten) to a field. Returns the improved text for review without saving.

Instructions

Ask ShipLocale's AI to rewrite copy for a field (e.g. shorten, punch up). Returns the improved text for review — it does NOT save anything; follow up with update_app_copy to apply it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdYesApp ID (GUID)
actionYesRewrite action, e.g. "improve", "shorten"
fieldTypeYes
sourceTextYesThe current text to rewrite
Behavior4/5

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

No annotations provided, but description clearly indicates read-only behavior by stating it returns text and does not save. Could add details on authorization or limits, but sufficient for the tool's simplicity.

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?

Extremely concise: two sentences that cover purpose, outcome, and usage guidance without any unnecessary information. Front-loaded with the core action.

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?

Covers the key aspects: purpose, input, output, and follow-up step. No output schema needed; for a simple tool, this is nearly complete. Could describe error handling or limits, but not critical.

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 75% and schema already provides descriptions for all parameters. The description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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?

Description clearly states the tool uses AI to rewrite copy and returns improved text for review. It distinguishes from siblings by explicitly naming the follow-up tool 'update_app_copy' to apply changes.

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 says 'it does NOT save anything' and instructs to follow up with 'update_app_copy' to apply the changes, providing clear when-to-use and when-not-to-use guidance with an alternative.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ShipLocale/shiplocale-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server