AppSkyline

Check your store listing and review status

get_store_metadata

Read-onlyIdempotent

Use this when someone asks about their own app's listing text per language, such as the title, subtitle, keywords or release notes, or whether the latest version is still in review or approved. Returns the metadata AppSkyline last synced for each locale, with the version, its review state and the keyword field's length against Apple's 100-character limit; longer texts are cut to 600 characters. Not for a live competitor listing.

Input Schema

TableJSON Schema

Name	Required	Description
`appId`	Yes	AppSkyline app id (uuid)
`store`	Yes	Store listing to read: ios-app-store, macos-app-store, google-play or microsoft-store
`locale`	No	Only this locale, written as in the listing such as en-US or it; every synced locale when absent

Output Schema

TableJSON Schema

Name	Required	Description
`appId`	Yes
`store`	Yes
`status`	Yes
`listings`	Yes	Metadata as last synced into AppSkyline, one row per locale; it may differ from what the store shows now. Long texts are cut to 600 characters.
`returned`	Yes
`truncated`	Yes
`localeFilter`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 28, 2026

changedInput schema / properties / appId / description

Previous value: -"Appskyline app id"New value: +"AppSkyline app id (uuid)"

changedInput schema / properties / locale / description

Previous value: -"Only return this locale (e.g. en-US, it)"New value: +"Only this locale, written as in the listing such as en-US or it; every synced locale when absent"

changedInput schema / properties / store / description

Previous value: -"Which store listing to read"New value: +"Store listing to read: ios-app-store, macos-app-store, google-play or microsoft-store"

addedOutput schema / properties / listings / description

Added value: +"Metadata as last synced into AppSkyline, one row per locale; it may differ from what the store shows now. Long texts are cut to 600 characters."

First observedAug 25, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already establish read-only/idempotent/no-destruction, and the description adds genuinely new behavioral context on top: the data is mirrored from the last AppSkyline sync (staleness), long texts are truncated at 600 characters, and it reports keyword length against Apple's 100-character limit. Those are non-obvious traits an agent would otherwise discover only at runtime.

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?

Front-loaded with the triggering condition, then the payload facts, then a one-clause exclusion. The middle sentence is dense with semicolon-joined clauses, but every clause carries information (returned fields, review state, keyword limit, truncation cap), so the size is justified.

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?

For a three-parameter, fully annotated read tool with an output schema, the description supplies everything needed to select and call it: trigger condition, scope, locale semantics, sync staleness and truncation behavior. It even over-delivers slightly on return values, which the output schema already covers.

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 appId, store and locale are all documented in the schema itself, which sets the baseline at 3. The description reinforces locale behavior (per-language text, every synced locale when absent) but adds no syntax or format detail beyond what the schema already states.

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?

The description names a concrete verb and resource: reading back per-locale listing text (title, subtitle, keywords, release notes) plus the review state of the latest version. It scopes the tool to "their own app's" data and ends with a contrastive boundary ("Not for a live competitor listing"), so an agent can separate it from listing-scraping tools.

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?

Usage is triggered explicitly ("Use this when someone asks about their own app's listing text per language... or whether the latest version is still in review") and one exclusion is given. However, the more ambiguous sibling get_store_listing is never named or contrasted, leaving the agent to guess between two closely related listing tools.

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

All AppSkyline tools Inspect

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

Need Help?