Skip to main content
Glama

CreativeScope — Mobile Game Ad Creative Intelligence

by ai.creativescope
OverviewDiscussionsAdmin

search_games

Search mobile games by name or category across global markets. Return identity, active ads and creatives in the last 30 days, and their lifetime estimated exposure as a delivery-heat reference, not 30-day incremental exposure. Supply keyword or category. Category accepts English or Chinese.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results; default 20; maximum 50.
offsetNoPagination offset; default 0.
regionNoOptional delivery region or ISO2 country code.
keywordNoSearch text in the user's original language. Supply keyword or category.
sort_byNoSort order: ad_heat, material_count, ad_count, downloads. The first value is the default.
categoryNoGame category in English or Chinese, such as strategy, RPG or casual. Supply keyword or category.
publisher_platformNoOptional delivery platform alias, such as facebook or tiktok.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / publisher_platform
      Added value: +{
+  "default": null,
+  "description": "Optional delivery platform alias, such as facebook or tiktok.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedInput schema / properties / region
      Added value: +{
+  "default": null,
+  "description": "Optional delivery region or ISO2 country code.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses that the returned exposure is lifetime estimated exposure, not 30-day incremental exposure, which is a meaningful behavioral nuance. It also states the requirement to supply keyword or category. It does not disclose pagination limits or default sort behavior, but the schema covers those.

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 compact and front-loaded: the main action and scope appear in the first sentence, followed by return-value clarification and input requirements. Every sentence earns its place, and the 'not 30-day incremental exposure' clarification is valuable rather than redundant.

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?

For a search tool with 7 optional parameters and no output schema, the description covers the core semantics: what is searched, what is returned, and the key input constraint. It does not explain the sort_by options or region semantics, but the schema covers those. The main gap is the lack of guidance on how this tool relates to sibling search tools.

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%, so the baseline is 3. The description adds a bit of meaning by explaining the keyword/category mutual exclusivity and the lifetime-vs-30-day exposure nuance, but it does not add much beyond the schema's parameter descriptions. The schema already documents defaults and allowed values.

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 ('Search') and resource ('mobile games'), and clarifies the scope ('across global markets'). It also names the return fields (identity, active ads, creatives, lifetime estimated exposure), which distinguishes it from sibling tools like get_game_detail or search_materials_v2. The explicit 'not 30-day incremental exposure' contrast further disambiguates its behavior.

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 gives clear usage context: supply keyword or category, and it notes that category accepts English or Chinese. It also clarifies the delivery-heat reference semantics. However, it does not explicitly state when to prefer this tool over siblings like search_materials_v2 or get_game_ads_v2, nor does it mention exclusions or alternatives.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources