Skip to main content
Glama

Appeak Pro: App Store Optimization

Check draft listing metadata

check_metadata
Read-onlyIdempotent

Checks a draft title, App Store subtitle or Google Play short description, keyword field, description and promotional text against the store's rules: character limits, words repeated across fields, wasted keyword-field space, policy words. Use it on any listing copy you write or review. No store call.

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": {
      "platform": "<platform>"
    },
    "name": "check_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
keywordsNoApp Store keyword field, comma separated
languageNoListing language, e.g. en, es-MX
platformYesios = App Store, android = Google Play
subtitleNoApp Store subtitle, or Google Play short description
descriptionNo
promotional_textNoApp Store only

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, idempotent, closed-world, non-destructive), and the description adds real value on top by clarifying that validation is local ('No store call') and enumerating the rule categories applied to the copy. It does not say whether unchanged/unchecked fields are simply skipped or how results are grouped, but for a pure validation tool this is a modest gap.

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?

A single front-loaded sentence does the specification work via a tight colon list, followed by two short sentences for usage and the local-execution note. No filler or restatement of the tool name.

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 7-parameter, single-required-parameter validator with no output schema, the definition conveys purpose, rules, and no-network behavior adequately. The remaining gap is that it never states that non-platform fields are optional and that checks run only on the fields supplied, which an agent must infer from 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 coverage is 71%, so the schema already explains keywords, language, platform enum, subtitle, and promotional_text. The description's field list mirrors the parameter names and restates that subtitle maps to Google Play short description and promotional_text is App Store only — both already in the schema. It adds no guidance on partial input or on the 'language' parameter's effect.

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 (checks) plus the exact resources (draft title, subtitle/short description, keyword field, description, promotional text) and the rule classes applied (character limits, cross-field repetition, wasted keyword space, policy words). This is concrete enough that an agent can distinguish it from audit_listing or check_keyword_ranks without opening any schema.

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?

'Use it on any listing copy you write or review' gives a clear trigger, and 'No store call' implicitly separates it from store-fetching siblings such as audit_listing. It stops short of naming an alternative or stating when-not-to-use (e.g., for live/published listings), so it misses the top band.

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