Skip to main content
Glama

CreativeScope — Mobile Game Ad Creative Intelligence

by ai.creativescope

get_game_rank_markets

List the countries, app-store categories, stores, and ranking types where a game appeared on a chart during a date range. Returns each observed dimension with best rank, latest rank, and ranked-day count. Ranking types are free, store-paid, and top-grossing. Only Google Play and iPhone App Store are exposed; iPad rankings are excluded. Date range defaults to the last 90 days and cannot exceed 365 days.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum dimension rows to return. Maximum 200; defaults to 100.
storeNoStore: all, google_play, or app_store. Defaults to all.
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.
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.0
Behavior3/5

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

Given no annotations, the description carries full burden. It discloses store platform exclusions (iPad), date range defaults and max, and ranking type definitions. However, it omits any mention of side effects, authentication requirements, read-only nature, or behavior for missing game IDs. This is adequate but not thorough.

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?

The description is concise with three sentences, no redundant information, and a clear front-loaded purpose. Every sentence adds necessary context without excess.

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?

Despite lacking an output schema, the description explains the return structure (dimensions with rank metrics). It mentions the limit parameter but doesn't specify pagination or ordering. For a simple list tool, this is mostly complete but could be slightly more detailed on edge cases.

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?

With 100% schema description coverage, the baseline is 3. The description adds value by clarifying store coverage (only Google Play and iPhone App Store, iPad excluded) and explaining ranking types more explicitly. This exceeds what the schema provides, earning a 4.

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 clearly states the tool lists countries, categories, stores, and ranking types where a game appeared on a chart within a date range. It specifies the returned metrics (best rank, latest rank, ranked-day count) and distinguishes from siblings like get_game_rank_trend by focusing on observed dimensions rather than trends.

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 provides implicit usage context (date range limits, store exclusions) but lacks explicit guidance on when to use this tool versus alternatives like get_game_rank_trend or search_advertisers. No when-not-to-use or alternative tool references are given.

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