Skip to main content
Glama
Sign In

AppmanAi

by com.appmanai
OverviewDiscussionsAdmin

Write store listing copy (AI)

generate_app_metadata
Read-only

Rewrite an app store listing — title, short and long description — optimised for the keywords you pass and the store it targets. Takes the current copy directly, not a package id, so you can iterate on drafts; use app_metrics_metadata first if you want to start from a live listing. Costs 15 credits.

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": {
      "store": "<store>",
      "country": "<country>",
      "description": "<description>"
    },
    "name": "generate_app_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
storeYesWhich app store: "android" (Google Play) or "ios" (App Store).
titleNoCurrent app title to rewrite from.
countryYesTwo-letter ISO country code, e.g. "US", "GB", "DE".
keywordsNoKeywords the new copy should target, up to 50.
languageNoLanguage code for the generated or localised text, e.g. "en".
competitorsNoCompetitor package ids to position against, up to 20.
descriptionYesCurrent app description to rewrite from, up to 4,000 characters.
category_tagNoCategory tag from list_categories.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds the economically important fact that 'it costs 15 credits' — a real pre-call consideration absent from structured fields. It also clarifies that input is draft copy rather than a live listing, implying nothing in the store is mutated, but it doesn't describe output shape or any limits on repeated calls.

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 tight sentences with the capability front-loaded, followed by the input-mode caveat, sibling routing, and cost. Every clause carries actionable information and nothing is repeated.

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 an 8-parameter generative tool with no output schema, the description names what is produced (title, short and long description) and covers input provenance and cost. It stops short of explaining how optional parameters like language, country, competitors, or category_tag influence results, leaving that to the schema.

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%, so every parameter (store enum, country ISO code, keywords, competitors, category_tag) is already documented. The description only restates that keywords and store drive the rewrite; it adds no syntax or constraint detail beyond the schema, so the baseline 3 applies.

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 set: 'Rewrite an app store listing — title, short and long description', and immediately scopes it as keyword- and store-targeted. Combined with the title, an agent can tell exactly what artifact this produces versus retrieval siblings like app_metrics_metadata.

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 names the alternative and the condition that selects it: 'use app_metrics_metadata first if you want to start from a live listing.' It also states the input-mode distinction ('takes the current copy directly, not a package id, so you can iterate on drafts'), which tells the agent when this tool is the right fit.

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

All AppmanAi toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources