Skip to main content
Glama

App audit

get_audit
Read-onlyIdempotent

Retrieve an app's ASO audit by country: rankings, listing fit, competition, verdict, fixes, top/gap phrases, competitors, and AI conclusions, with one market detailed and others summarized.

Instructions

Where the app stands per tracked country and overall, 0-100 (countries weighted by market potential): rankings (visibility of each checked phrase's rank, weighted by demand), listing (how well the country's own listing holds the searched words; localized says whether it is in the country's language), competition (how beatable the apps ranked above are), a verdict (pivot = change keywords, localize = the listing shown is in another language and misses the searches, align = fine-tune, fine), deterministic issues with the step that fixes each (action: keywords, names, names_localize, copy, copy_localize, screens, screens_localize, store), the top-10 and gap phrases, main competitors, and the AI conclusions (headline, reason, takeaways) of the last run_audit plus a cross-country summary. One country is returned in full (country, default the main one); the others as one line each. Demand is real popularity when connected (demandSource), else estimated volume.

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": {
      "projectId": "<projectId>"
    },
    "name": "get_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoMarket = ISO 3166-1 alpha-2 country code, e.g. "us", "de".
projectIdYesProject id (from get_overview).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • addedInput schema / properties / country
      Added value: +{
      +  "description": "Market = ISO 3166-1 alpha-2 country code, e.g. \"us\", \"de\".",
      +  "pattern": "^[A-Za-z]{2}$",
      +  "type": "string"
      +}
  2. First observedv0.1.7

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds meaningful behavior the annotations do not: one country returned in full while the rest are collapsed to one line, the demandSource-vs-estimated-volume fallback, and the verdict vocabulary (pivot/localize/align/fine) that governs how results should be interpreted.

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

Conciseness3/5

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

The purpose is front-loaded, which is good, but the body is a single ~150-word sentence with deeply nested parentheses enumerating every sub-object and every action enum. The information is valuable; the packaging makes it hard to scan and would be far more usable as a short list of returned sections.

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 carries the full burden of explaining return values and does so thoroughly, including the AI conclusions, cross-country summary and per-country truncation. The remaining gap is state-dependent behavior: it never says what is returned when run_audit has not yet been executed or when a country is not tracked.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description earns above that by documenting the behavioral default for country ('default the main one') and the full-vs-abbreviated return split that depends on it. It does not repeat the ISO code pattern, which the schema already handles well.

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?

The opening clause 'Where the app stands per tracked country and overall, 0-100' states the resource and the nature of the result (a score), and the phrase 'of the last run_audit' distinguishes it from the compute-side sibling. It is not a clean verb+resource statement and never says explicitly 'retrieves the stored audit', so an agent must infer read semantics, but the intent is unambiguous.

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?

Mentioning 'the last run_audit' implies the prerequisite that an audit must have been run first, which is real guidance. However, there is no explicit when-to-use framing, no exclusion (e.g. use get_overview for project-level KPIs, get_term_detail for a single phrase), and no statement of what happens when no audit exists yet.

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

Deploy Server

Other Tools