Skip to main content
Glama

CreativeScope — Mobile Game Ad Creative Intelligence

by ai.creativescope

generate_weekly_creative_brief

Generate a compact creative brief from recent high-signal mobile game ads. Use this for weekly inspiration, hook mining, competitor creative planning, and UA brainstorming. Creative tag fields are normalized to English in the result. Example: 'Create this week's puzzle-game creative brief for Facebook.'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
genreNoGame genre or sub-genre in the user's original language, for example match-3 or puzzle. Chinese source-label expansion is internal.
limitNoNumber of representative creatives to include. Maximum 20.
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_7_days.

TDQS

A3.9/5.0
Behavior3/5

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

No annotations exist, so the description carries the burden. It discloses that 'Creative tag fields are normalized to English in the result' but does not mention nondestructive nature, authentication, rate limits, or output structure. Adequate but minimal.

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 two sentences plus an example, all front-loaded and concise. Every sentence adds value: purpose, use cases, and a concrete example. No wasted words.

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?

With 6 parameters and no output schema, the description provides adequate context for basic usage (use cases, example) but lacks detail on what a 'brief' contains or the output format. Leaves some uncertainty for the agent.

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%; parameter descriptions in the schema already explain each field. The description adds marginal value by showing usage in the example, but does not deepen meaning beyond the schema. Baseline 3 is appropriate.

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 verb+resource: 'Generate a compact creative brief from recent high-signal mobile game ads.' It clearly distinguishes from siblings like search_creatives or get_creative_detail by focusing on brief generation.

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 lists explicit use cases: 'weekly inspiration, hook mining, competitor creative planning, and UA brainstorming.' It provides an example ('Create this week's puzzle-game creative brief for Facebook') but does not exclude alternative tools or scenarios.

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