Skip to main content
Glama
qalvinahmad

ads-mcp

by qalvinahmad

AdMob network report

admob_network_report
Read-onlyIdempotent

Retrieve AdMob network performance data including revenue, impressions, eCPM, and clicks. Filter by dimensions like date, app, ad unit, and country to analyze trends.

Instructions

Generate an AdMob Network report (revenue, impressions, eCPM, ...).

Dimensions: DATE, MONTH, WEEK, AD_UNIT, APP, AD_TYPE, COUNTRY, FORMAT, PLATFORM, MOBILE_OS_VERSION, GMA_SDK_VERSION, APP_VERSION_NAME, SERVING_RESTRICTION. Only one time dimension (DATE/MONTH/WEEK) per request.

Metrics: AD_REQUESTS, CLICKS, ESTIMATED_EARNINGS, IMPRESSIONS, IMPRESSION_CTR, IMPRESSION_RPM, MATCHED_REQUESTS, MATCH_RATE, SHOW_RATE. Monetary values are returned already divided from micros into currency units.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rawNoReturn the raw API JSON instead of a formatted table
metricsNoMetrics to include (defaults to IMPRESSIONS, CLICKS, ESTIMATED_EARNINGS)
end_dateNoEnd date in YYYY-MM-DD (defaults to start_date)
time_zoneNoIANA timezone, e.g. "Asia/Jakarta"
account_idNoAdMob publisher ID, e.g. "pub-1234567890123456". Omit to use the first account of the authorized user.
dimensionsNoDimensions to group by
start_dateYesStart date in YYYY-MM-DD
currency_codeNoISO 4217 currency code for monetary metrics, e.g. "USD"
max_report_rowsNoMax rows to return (1-100000)
sort_conditionsNoSort conditions
dimension_filtersNoDimension filters to apply
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds behavioral details: only one time dimension per request, and monetary values are returned from micros to currency units. This supplements annotations well.

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 and front-loaded: a lead sentence, then lists of dimensions/metrics with relevant constraints. No fluff, every sentence adds value.

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 the tool's complexity (11 params, no output schema), the description covers purpose, available values, constraints, and output formatting. It lacks details on response structure but is otherwise complete.

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%, baseline 3. The description enumerates valid values for dimensions and metrics, and adds a constraint (one time dimension per request), providing meaningful extra context beyond the schema.

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 'Generate an AdMob Network report' with a specific verb and resource. It lists dimensions and metrics, differentiating it from sibling tools like admob_mediation_report.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It only states what it does, without exclusions or comparisons to siblings like admob_mediation_report.

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

Install Server

Other Tools

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/qalvinahmad/ads-mcp'

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