Skip to main content
Glama

Recao

by app.recao

get_competitor_ads

Read-onlyIdempotent

Get all Apple App Store ads a competitor has run (EU storefronts, up to 1 year back), with creative copy, placements, formats, and an inferred winner analysis: ads sorted by how long they've been running (longevity = the advertiser keeps paying = likely converting). Source: official Apple Ad Repository (DSA transparency data).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesappId or developerId from search_app_advertiser
typeNoAPP
countriesNoEU country codes to filter (default: all 25). Available: AT,BE,BG,HR,CY,CZ,DK,EE,FI,FR,DE,GR,HU,IE,IT,LV,LU,NL,PL,PT,RO,SK,SI,ES,SE
datePresetNoLAST_YEAR

TDQS

A4/5.0
Behavior4/5

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

Beyond annotations (readOnly, idempotent, open world), the description adds the data source (Apple Ad Repository, DSA transparency data), sorting logic (by longevity indicating likely converting), and constraints (EU storefronts, 1-year lookback). This provides valuable behavioral context.

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, front-loads the purpose, and includes essential details without fluff. Every part serves a purpose, making it highly concise and well-structured.

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 no output schema and 4 parameters, the description covers core functionality, data source, and output characteristics (sorted list with winner analysis). It lacks details on pagination or response format, but overall is fairly complete for a read-only data retrieval tool.

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?

With 50% schema description coverage, the description does not add detailed meaning for parameters beyond what's in the schema. It mentions that id comes from search_app_advertiser, which is useful, but overall parameter semantics are minimally enhanced.

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 retrieves all Apple App Store ads a competitor has run, with specific attributes like creative copy, placements, formats, and a winner analysis sorted by ad longevity. It distinguishes from siblings like get_ad_details and get_playbook by focusing on aggregate competitor intelligence.

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 implies usage is contingent on first obtaining an id from search_app_advertiser, but it does not explicitly state when to use this tool over alternatives or provide when-not-to-use guidance. The context from sibling tools is not leveraged in the description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Recao 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.4/5.0
Disambiguation5/5

Each tool has a clear, distinct purpose. The status checkers (assemble_status, clips_status) are differentiated by the job type they monitor. Memory tools (index, note, recall) are distinct operations. Competitor ad tools (search, get ads, get details) and video generation pipeline (avatar, clips, assembly) are well-separated.

Naming Consistency5/5

All tools use consistent snake_case with a verb_noun or noun_verb pattern (e.g., assemble_video, get_competitor_ads, memory_index). No mixing of conventions, making the tool names predictable and easy to understand.

Tool Count5/5

With 17 tools, the server covers account management, memory, competitor research, and video generation without being overwhelming. The count is well-scoped for its functionality, neither too sparse nor too heavy.

Completeness4/5

The toolset covers the core workflows: account setup (sign_up, upgrade, whoami), memory (CRUD), competitor analysis (search, get ads, details), and video ad creation (avatar, clips, assembly). Minor gaps like lacking a delete memory tool are acceptable given the domain focus.

Resources