Skip to main content
Glama
jimsimoy

AdMob MCP

generate_mediation_report

Create a mediation performance report for AdMob, showing earnings, impressions, and clicks across ad sources for a date range and account.

Instructions

Generate an AdMob mediation performance report (earnings across ad sources).

account_name looks like 'accounts/pub-1234567890123456'. start_date/end_date
are 'YYYY-MM-DD', inclusive.

dimensions default to ["DATE", "AD_SOURCE"]; valid values: DATE, MONTH,
WEEK, AD_SOURCE, AD_SOURCE_INSTANCE, AD_UNIT, APP, MEDIATION_GROUP,
COUNTRY, FORMAT, PLATFORM, MOBILE_OS_VERSION, GMA_SDK_VERSION,
APP_VERSION_NAME, SERVING_RESTRICTION.

metrics default to ["ESTIMATED_EARNINGS", "IMPRESSIONS", "CLICKS"]; valid
values: AD_REQUESTS, CLICKS, ESTIMATED_EARNINGS, IMPRESSIONS,
IMPRESSION_CTR, MATCHED_REQUESTS, MATCH_RATE, OBSERVED_ECPM.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
metricsNo
end_dateYes
dimensionsNo
start_dateYes
account_nameYes
max_report_rowsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior2/5

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

With no annotations present, the description carries the full burden for behavioral transparency. It indicates that the tool generates a report and lists valid query values, but it never states whether the operation is read-only, whether it has side effects, or how results are returned and paginated.

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 well structured: a one-line purpose followed by short parameter, default, and value lists. There are no redundant sentences or filler.

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?

The combination of description and input schema provides enough to make a basic call: required parameters are formatted, defaults and valid values are listed, and an output schema exists. It falls short only on max_report_rows semantics and report-shaping details such as pagination or timezone.

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?

The description explains the format of account_name, start_date, and end_date, and enumerates valid and default values for dimensions and metrics, covering most parameters. max_report_rows is left without any explanation, and the meaning of individual dimension or metric values is not expanded.

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 opens with a specific verb and resource: 'Generate an AdMob mediation performance report,' and the parenthetical clarifies it covers earnings across ad sources. This is enough to distinguish it at a high level from sibling reporting tools.

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 includes concrete usage guidance: account_name format, inclusive date format, and defaults for dimensions and metrics. It does not explicitly state when to choose this tool over generate_network_report, so some situational guidance is missing.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jimsimoy/admob-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server