Skip to main content
Glama

CreativeScope — Mobile Game Ad Creative Intelligence

by ai.creativescope

get_game_rank_trend

Get one mobile game's daily app-store ranking performance over a date range. Returns free, store-paid, and top-grossing ranking series with best/latest rank and the matched country, category, and store. Use mode=best to select the game's best daily rank across supported countries and categories, or mode=exact for one country/category/store combination. Supported stores are Google Play, iPhone App Store, and all (Google Play plus iPhone App Store). Date range defaults to the last 90 days and cannot exceed 365 days.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoQuery mode: best or exact. Defaults to best.
storeNoStore: all, google_play, or app_store. Used as a constraint in both modes; defaults to all.
countryNoISO 3166-1 alpha-2 country code. Used by exact mode; defaults to US.
date_toNoEnd date in YYYY-MM-DD. Defaults to today.
game_idYesEncrypted game ID returned by search_advertisers or as game_id/advertiser_id in other results.
categoryNoApp-store category. Used by exact mode; defaults to all categories.
date_fromNoStart date in YYYY-MM-DD. Defaults to 89 days before date_to.
rank_typesNoRanking types: free, store_paid, grossing. Defaults to all three.

TDQS

A4.5/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses return fields (rank series, best/latest rank, country, category, store), modes, supported stores, and date constraints. Lacks explicit read-only hint but implied.

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 sentences, each essential. First sentence states purpose, second explains modes, third lists supported stores and date constraints. No redundancy.

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?

Given 8 parameters and no output schema or annotations, the description fully explains all parameter behaviors, defaults, constraints, and return value structure. No gaps.

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?

Schema coverage is 100%, baseline 3. Description adds value by explaining how parameters interact (e.g., country/category used in exact mode) and defaults. Goes beyond schema.

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?

Description starts with a clear verb+resource: 'Get one mobile game's daily app-store ranking performance over a date range.' It specifies what is returned and distinguishes from sibling tools like get_game_rank_markets by focusing on trend data.

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?

Explains two modes (best vs exact) with explicit guidance on when to use each. Also covers default date range and maximum range. Does not explicitly list alternatives from siblings, but context is sufficient.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool serves a distinct purpose: searching creatives, advertiser profiles, game rankings, image similarity search workflow, etc. Overlaps like find_similar_creatives vs submit_reference_image_search are clearly separated by whether using an existing creative or a new image URL.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (e.g., get_creative_detail, search_advertisers, submit_reference_image_search) with snake_case. No mixed conventions or vague verbs.

Tool Count5/5

12 tools cover the domain of mobile game ad intelligence without redundancy. The count feels appropriate—enough to handle common tasks (search, detail, rankings, image search) without overwhelming.

Completeness5/5

The tool set covers essential workflows: finding creatives via text or image, analyzing advertiser and game rankings, retrieving creative details and insights, and generating briefs. The async image search workflow is fully supported with submit, status, and results tools.

Resources