Skip to main content
Glama

CreativeScope — Mobile Game Ad Creative Intelligence

by ai.creativescope

get_creative_rankings

Get global or genre-level rising creative rankings by day, week, or month, or evergreen creative rankings from the monthly snapshot; platform and country filters are not supported. Evergreen data is monthly only; day/week requests are normalized to month and disclosed in request_echo. Use this to answer what's rising this week, what evergreen creatives keep working, or which hook patterns repeat in a genre. For platform- or country-filtered discovery, use search_creatives and do not describe those results as an official rising or evergreen ranking. Creative tag fields are normalized to English in the result. Example: 'Which SLG creatives are rising this month?'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesRanking type: rising or evergreen.
genreNoOptional genre/category filter in the user's original language, for example match-3 or SLG. Chinese source-label expansion is internal.
limitNoNumber of ranked creatives to return. Maximum 20.
periodYesRanking period: day, week, or month. Evergreen supports month only; other values are normalized to month.

TDQS

A4.4/5.0
Behavior4/5

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

Given no annotations, description discloses key behaviors: platform/country filters unsupported, evergreen monthly-only, day/week normalized to month with disclosure in request_echo, creative tags normalized to English. Missing details on return format or pagination, but for a read-only ranking tool, this is adequate.

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 purpose, then constraints, usage guidance, and an example. Each sentence adds unique value with no redundancy. Slightly long but efficient for the information density.

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

Completeness3/5

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

No output schema, and description does not explain the return structure (e.g., fields returned, ranking order). While the tool is straightforward, the missing output format could hinder agent understanding. Otherwise, covers constraints and usage well.

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% with descriptions. Description adds context: period normalization for evergreen, genre in original language (Chinese expansion internal), limit maximum 20. These details go beyond the raw schema definitions.

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 clearly states it gets global or genre-level rising or evergreen creative rankings by day, week, or month. The verb 'get' and resource 'creative rankings' are specific, and the scope is explicitly defined, distinguishing it from siblings like search_creatives.

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

Usage Guidelines5/5

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

Explicitly says when to use (e.g., 'what's rising this week') and when not to use (platform/country filtering), and provides an alternative: 'use search_creatives'. Also warns against mislabeling results as official rankings.

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