Skip to main content
Glama

Dashboard: every app at a glance

get_dashboard
Read-onlyIdempotent

Retrieve cross-market ASO performance for every tracked App Store and Google Play app, including visibility, keyword rankings, audit scores, 7/30/90-day changes, downloads, and conversions.

Instructions

Every tracked app of both stores with its search measures today over all tracked markets together: visibility (0-100, the demand-weighted share of search attention on the audit's rank curve; whole points from 1 up, one decimal below, at least 0.1 when any tracked search shows the app and 0 only when none does; null without the scoring bundle or before release), searches (phrase x market) in the top 10 and top 3, average rank of the ranked ones, the latest audit score, and how each moved over 7, 30 and 90 days (null when nothing was checked back then; avgRank negative = better). Each phrase keeps its last checked rank between checks. Own apps with store analytics connected add downloads and conversion (downloads / page views) per period, ending on the last day the store reported, with the change vs the period before (null when the store reported under 80% of those days). trend: weekly points of the last 90 days. Local data.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_dashboard"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.3

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world behavior, but the description adds substantive context the annotations don't: null semantics for scoring bundles, release timing, and sparse store reporting; the 80% reporting threshold; caching of the last checked rank between checks; and that data is local. That is real behavioral disclosure beyond structured fields.

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

Conciseness2/5

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

It is effectively one enormous run-on sentence stitched together with semicolons and long parentheses, including a buried scoring-curve definition and decimal-formatting trivia. The payload is front-loaded, but structure is poor and several clauses could be cut without losing callable information.

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 burden of explaining return values and does so thoroughly: visibility, search counts, average rank, audit score, 7/30/90-day movement, downloads and conversion, and the trend series. What is missing is usage routing relative to sibling tools, not return-value detail.

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?

The tool takes no parameters, so the schema has nothing to explain and the description correctly spends no effort on input semantics. It instead specifies what the returned measures mean, which is the useful substitute here.

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 states a specific resource and scope: every tracked app across both stores with today's search measures over all tracked markets. It is clear what the tool returns, but nothing distinguishes it from look-alike siblings such as get_overview or get_app_insights.

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 named alternative. An agent must infer from the word 'Dashboard' that this is the broad first-look tool rather than a per-app or per-term drill-down.

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