Skip to main content
Glama

AppSkyline

by com.appskyline.mcp
OverviewDiscussionsAdmin

Show keyword rank history

get_keyword_history
Read-onlyIdempotent

Use this when someone asks how their app's ranking for a keyword has changed over time in one store and country. Returns the app's rank on each date AppSkyline stored a search snapshot, newest first, up to 365 rows; tracked keywords are re-checked weekly. Not for today's live rank.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesSearch term to read history for, 1 to 200 characters
appIdYesAppSkyline app id (uuid)
limitNoSnapshots to return, newest first, from 1 to 365; defaults to 365
storeYesStore to read: ios-app-store, macos-app-store, google-play or microsoft-store; the app needs an id on that store
countryYesTwo-letter store country code such as US or IT (required)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
appYes
termYes
storeYes
statusYes
countryYes
returnedYes
snapshotsYesOne row per stored search snapshot, newest first; rank is null when the app was not in that snapshot
truncatedYes
totalSnapshotsYes
totalSnapshotsIsLowerBoundYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / appId / description
      Previous value: -"Appskyline app id"New value: +"AppSkyline app id (uuid)"
    • changedInput schema / properties / country / description
      Previous value: -"Two-letter country code (e.g. US, IT)"New value: +"Two-letter store country code such as US or IT (required)"
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of history rows to return (newest first)"New value: +"Snapshots to return, newest first, from 1 to 365; defaults to 365"
    • changedInput schema / properties / store / description
      Previous value: -"Which store to check"New value: +"Store to read: ios-app-store, macos-app-store, google-play or microsoft-store; the app needs an id on that store"
    • changedInput schema / properties / term / description
      Previous value: -"Search term"New value: +"Search term to read history for, 1 to 200 characters"
    • addedOutput schema / properties / snapshots / description
      Added value: +"One row per stored search snapshot, newest first; rank is null when the app was not in that snapshot"
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavioral context: rank is returned per stored snapshot, newest first, capped at 365 rows, and tracked keywords are only re-checked weekly. That freshness cadence is exactly what an agent needs to interpret stale results.

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

Conciseness5/5

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

Three tight sentences, front-loaded with the usage trigger, then return shape, then the exclusion. Every sentence earns its place with no filler.

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

Completeness5/5

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

With an output schema present, the description needn't explain the response payload, and annotations cover safety. Combined with the freshness cadence and row cap, an agent has everything required to call this correctly and interpret the result.

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 all five parameters (including term, store enum, country, limit) are already documented in the schema. The description restates the one-store/one-country scope but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource (retrieve an app's keyword rank history over time) and pins the scope to one store and one country. It is clearly distinguishable from siblings like get_keyword_rank (live rank) and get_keyword_overview.

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

Usage Guidelines4/5

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

Gives an explicit trigger ('when someone asks how their app's ranking ... has changed over time') and an explicit exclusion ('Not for today's live rank'). It stops short of naming the alternative tool an agent should use for live rank, so it is clear but not fully routed.

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

All AppSkyline toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources