Skip to main content
Glama

CreativeScope — Mobile Game Ad Creative Intelligence

by ai.creativescope
OverviewDiscussionsAdmin

get_store_game_rank_trend

Get game-level official daily chart trends using a game token or an app identifier resolved through the official package mapping. Best mode selects leading dimensions across Google Play and iPhone App Store; exact mode fixes store, country and category. Includes current-day realtime data when available. Returns daily ranks, first-entry flags and optional 24-hour curves.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNobest selects the strongest observed dimensions across both stores; exact fixes platform, country and category. Defaults to exact when country_code is supplied, otherwise best.
date_toNoEnd date, YYYY-MM-DD; defaults to today unless explicitly required. Maximum range 365 days.
game_idNoGame token from search_games or store rankings. Queries every associated official-store package, matching the game-level API.
platformNoStore for exact mode: 1=Google Play, 2=iPhone App Store. Defaults to the supplied app identifier's store, otherwise Google Play.
date_fromNoStart date, YYYY-MM-DD. Follow this tool's required-date and range constraints.
categoriesNoOfficial store category code or canonical category name. Use get_store_game_rank_filter to obtain valid platform-specific values.
max_seriesNoMaximum chart series in best mode; default 20, maximum 50.
rank_typesNoArray of chart types: 0=free, 1=paid, 2=grossing. Omit for all.
country_codeNoISO 3166-1 alpha-2 country code, such as US or TR. Follow this tool's country-selection rules.
package_nameNoOptional Android package name or numeric iOS app ID. Resolves the owning game through the official package mapping; supply this or game_id, not both.
include_rank_curveNoInclude a fixed 24-entry hourly rank curve for each day; default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / game_id
      Added value: +{
+  "default": null,
+  "description": "Game token from search_games or store rankings. Queries every associated official-store package, matching the game-level API.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedInput schema / properties / max_series
      Added value: +{
+  "default": null,
+  "description": "Maximum chart series in best mode; default 20, maximum 50.",
+  "type": [
+    "integer",
+    "null"
+  ]
+}
    • addedInput schema / properties / mode
      Added value: +{
+  "default": null,
+  "description": "best selects the strongest observed dimensions across both stores; exact fixes platform, country and category. Defaults to exact when country_code is supplied, otherwise best.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedInput schema / properties / package_name / default
      Added value: +null
    • changedInput schema / properties / package_name / description
      Previous value: -"Required Android package name or numeric iOS app ID. Numeric identifiers imply iOS."New value: +"Optional Android package name or numeric iOS app ID. Resolves the owning game through the official package mapping; supply this or game_id, not both."
    • changedInput schema / properties / package_name / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • addedInput schema / properties / platform
      Added value: +{
+  "default": null,
+  "description": "Store for exact mode: 1=Google Play, 2=iPhone App Store. Defaults to the supplied app identifier's store, otherwise Google Play.",
+  "type": [
+    "integer",
+    "null"
+  ]
+}
    • removedInput schema / required
      Removed value: -[
-  "package_name"
-]
  2. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses current-day realtime data availability, return contents (daily ranks, first-entry flags, optional 24-hour curves), and the package-mapping resolution behavior. It stops short of discussing rate limits or failure cases, but the core read behavior is transparent.

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 dense sentences front-load the primary purpose, then explain modes, data freshness, and return shape without redundancy. Every clause adds useful information, which is appropriate for a tool with 11 parameters.

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?

The schema covers all parameters and the description supplies the key behavioral logic: best/exact mode selection, package resolution, realtime inclusion, and return components. Without an output schema, a bit more detail about the exact response structure or caveats would make it fully complete, but the current combination supports correct tool invocation.

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 the baseline is 3. The description reinforces mode semantics already present in the schema (best vs exact) and summarizes outputs, but it adds little new meaning about individual parameters beyond what the schema already documents.

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 states a specific action ('Get game-level official daily chart trends') and identifies the input paths (game token or app identifier via package mapping). It also differentiates the tool's scope by explaining best vs exact modes, making it distinct from sibling tools like get_store_game_rank and get_game_trend.

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?

The description explains how to choose between best and exact modes, and implies that game_id or package_name should be supplied, but it never explicitly names sibling alternatives or states when this tool should be preferred over them. The guidance is internal to the tool's modes rather than tool-selection guidance.

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

All CreativeScope — Mobile Game Ad Creative Intelligence 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