Skip to main content
Glama

Appeak Pro: App Store Optimization

Find an app's search competitors

find_competitors
Read-onlyIdempotent

The apps that rank above this one in the searches its listing is written for, with the searches each one tops.

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": "find_competitors"
  }
}

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

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds real value beyond that by disclosing the return content: a set of competitor apps plus the searches each one tops. It does not state how many competitors are returned, how 'ranks above' is computed, or how the input link is resolved.

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, front-loaded sentence with no filler, but it is a bare noun phrase with no verb, which reads as a return-value summary rather than a statement of what the tool does. Slightly harder to parse than a full clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only tool with 100% schema coverage and no output schema, the main burden is describing the return shape, which it partly does. Gaps remain around result volume, how the search set is derived, and behavior when the store URL has no country segment.

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 both parameters are fully documented with format and defaulting already. The description adds no syntax, validation, or URL-format meaning beyond what the schema states, so the baseline of 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?

Names a specific resource and scope: the apps ranking above this one for the searches its listing targets, plus the searches each tops. It is clearly a competitor-discovery resource rather than a rank check like check_keyword_ranks, but the phrase 'the searches its listing is written for' is ambiguous (metadata keywords? indexed queries?) and no sibling is named to disambiguate.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no alternative named; an agent must infer from the title that this is for competitor research rather than for checking its own ranks. The only conditional guidance in the whole definition lives in the schema (country defaulting), not the description.

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