Skip to main content
Glama

Appeak Pro: App Store Optimization

Check if ChatGPT recommends an app

check_ai_visibility
Read-only

Asks ChatGPT (with web search) the question people ask when looking for an app like this one, e.g. "What's the best budget planner app?", and says whether it names the app, at what position, and which apps it recommends instead. One question on one assistant; answers are reused for a week.

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

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?

Beyond the annotations, it discloses that the check makes a live web-search-backed ChatGPT call, covers one question on one assistant only, and that answers are reused for a week — which usefully explains why repeated calls are cheap and why idempotentHint is false. It stops short of noting latency, cost, or what happens if ChatGPT is unreachable.

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?

The core behavior and the concrete example question are front-loaded, and the caching caveat is a short trailing clause. It is a single long sentence, but every clause carries information; only minor tightening is possible.

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 return-value burden and does so by naming the three results (named or not, position, competitor apps). Combined with the caching note and the schema's country default, an agent has what it needs; missing only error/latency expectations for an open-world call.

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 100%, so store_url format and the two-letter country fallback chain are already fully documented in the schema. The description adds no meaning beyond that, which is the baseline case when the schema does the work.

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 description states a specific action (ask ChatGPT with web search a buyer-intent question) and a specific result (whether the app is named, at what position, and which apps are recommended instead). That makes it clearly distinct from a store-rank or metadata tool, but it never names or contrasts a sibling, so an agent must infer the boundary itself.

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 implied by the framing ('the question people ask when looking for an app like this one'), so an agent can infer this is for AI-assistant visibility checks. There is no explicit when-to-use/when-not guidance and no routing to alternatives such as check_keyword_ranks or check_metadata.

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