Skip to main content
Glama

Appeak Pro: App Store Optimization

Audit an app store listing

audit_listing
Read-onlyIdempotent

Free ASO audit of a live App Store or Google Play listing: each part (title, subtitle or short description, description, screenshots, ratings, localization) graded Working / Worth a look / Fix this with the reason, the listing's facts, and the biggest gaps. Rule-based, from the public listing.

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_url": "<store_url>"
    },
    "name": "audit_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoTwo-letter store country (us, gb, de...). Defaults to the link's country, else us.
store_urlYesThe app's App Store or Google Play link, e.g. https://apps.apple.com/us/app/id570060128

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world and non-destructive behavior, so the description needn't restate safety. It does add real context the annotations lack: the audit is rule-based, operates only on the public listing (no private/analytics data), and is free — implying deterministic, repeatable results and no account requirements. It doesn't cover rate limits or what happens with an invalid or region-locked link.

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?

A single dense sentence front-loads what the tool is and what it returns; every clause adds information (graded parts, grade labels, reasons, facts, gaps, method). The colon-separated enumeration is readable but close to overloaded, so slightly short of ideal.

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?

With no output schema, the description usefully explains the shape of the result: per-part grades on a three-level scale, the reason, listing facts, and the biggest gaps. Combined with full schema coverage for the two inputs, an agent has enough to call this correctly; only edge-case behavior (invalid link, unsupported store) is unstated.

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%, with both store_url and the country fallback chain (link's country, else us) documented in the schema. The description adds nothing about either parameter, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb and resource — grading the parts of a live App Store or Google Play listing (title, subtitle/short description, description, screenshots, ratings, localization) and returning reasons, listing facts and gaps. That scope is specific enough to separate it from siblings like check_metadata or check_keyword_ranks, though no sibling is named.

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

Usage Guidelines3/5

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

Usage is only implied by 'of a live App Store or Google Play listing' and 'from the public listing' — i.e. the listing must be live and public. There is no explicit statement of when to prefer this over check_metadata or check_ai_visibility, and no exclusions or prerequisites beyond requiring a store link.

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