Skip to main content
Glama
storelift-mcp

storelift-mcp

AI visibility results

get_ai_visibility
Read-onlyIdempotent

Measure app mentions in a dated sample of AI assistant answers and read its question count to assess AI visibility without treating skipped questions as zero scores.

Instructions

App mentions in a dated sample of AI assistant answers; this does not reproduce what every user sees. The ai:read scope is required. A question that could not be asked is not a zero score. Read the dated sample and its question count; it is not a universal ranking or a measure of all consumer answers.

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": {
      "appId": "<appId>"
    },
    "name": "get_ai_visibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesapp id from list_apps
countryNocountry code, e.g. tr, us (defaults to the app's first country)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.0
    • changedInput schema / properties / country / description
      Previous value: -"country code, e.g. tr, us"New value: +"country code, e.g. tr, us (defaults to the app's first country)"
  2. First observedv1.1.1

TDQS

B3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: results are a dated sample rather than a reproduction of every user's view, the ai:read scope is required, and an unaskable question is not recorded as a zero. It still omits return format and pagination, keeping it below a 5.

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, but the text is four clipped semicolon-joined fragments and the disclaimer about not representing all users is stated twice ('does not reproduce what every user sees' and 'not a measure of all consumer answers'), which wastes space without adding precision.

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?

With no output schema and two simple params, the description does mention what to consult (the dated sample and its question count), which is helpful. It does not say whether a prior run_ai_visibility_check is required for data to exist or what the response shape looks like, which are the main remaining unknowns for a read tool.

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% and the schema documents both appId ('app id from list_apps') and the country default. The description adds no parameter-level meaning, so the baseline 3 applies.

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

Purpose3/5

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

The description identifies the resource as 'app mentions in a dated sample of AI assistant answers', which is specific about the data, but never states the verb (returns/reads existing results) and never distinguishes it from the sibling run_ai_visibility_check, which plausibly triggers a new check. An agent can guess the resource but must infer whether this reads cached results or produces them.

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 explicit when-to-use guidance and no named alternative. 'Read the dated sample and its question count' hints that this is the retrieval step rather than the run step, but the agent is left to infer that distinction from the sibling name alone, which the instructions say not to rely on.

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