Skip to main content
Glama

CreativeScope — Mobile Game Ad Creative Intelligence

by ai.creativescope

search_creatives

Search mobile game ad creatives by keyword or visual-description-like natural language. For an English request, send the original English concepts only. The service internally expands genre, hook, mood, art-style, and gameplay-mechanic concepts to Chinese source-label equivalents for retrieval; generated translations must not be inserted into the public request. Use this for finding UGC-style ads, winning creatives, opening hook examples, playable ads, and platform/country/genre slices. Results include the original creative asset as media_url when available. Creative tag fields are normalized to English in the result. Example: 'Find UGC-style match-3 video ads in the US.'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
genreNoGame genre or sub-genre in the user's original language, for example match-3, puzzle, or SLG. Chinese source-label expansion is internal.
limitNoNumber of creatives to return. Maximum 20.
queryYesNatural-language search query in the user's original language. Do not append generated Chinese translations to an English query; the service performs Chinese source-label expansion internally.
formatNoCreative format: image, video, or playable.
countryNoISO 3166-1 alpha-2 country code, for example US, JP, KR, GB.
platformNoAd platform filter. Supported values: facebook, instagram, messenger, audience_network, threads, admob, youtube, tiktok, mintegral, unity, applovin, ironsource, vungle, pangle.
date_rangeNoDate range. Supports last_7_days, last_30_days, last_90_days, or 'YYYY-MM-DD..YYYY-MM-DD'. Defaults to last_90_days.
orientationNoOptional creative orientation: portrait, landscape, or square. For video, this is derived from existing media width and height metadata.

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description fully discloses internal Chinese source-label expansion, that results include media_url and normalized English tags, and prohibits user-generated translations. No contradictions detected.

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: two sentences plus an example. Every sentence adds essential information: purpose, internal behavior, use cases, output features, and example. No redundancy or fluff.

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?

Given 8 parameters, 100% schema coverage, no output schema, the description covers usage context, internal processing, and output traits (media_url, normalized tags). It lacks details on other result fields but is sufficient for a search tool.

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%, so baseline is 3. The description adds value by explaining the internal expansion rule and giving an example query, clarifying how to use the 'query' parameter and the role of 'genre'.

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 action (search) and resource (mobile game ad creatives), specifies query methods (keyword or natural language), and provides an example. This distinguishes it from siblings like find_similar_creatives or get_creative_detail.

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?

The description explicitly lists use cases (UGC-style ads, winning creatives, etc.) and provides an example query. It also warns against inserting Chinese translations into the English query. However, it does not explicitly contrast with alternative tools like find_similar_creatives.

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