Skip to main content
Glama
AdSense-MCP-Server

AdSense-MCP-Server

by AppsYogi-com

adsense_generate_report

Generates detailed AdSense performance reports with custom dimensions, metrics, date ranges, filters, and sorting to analyze earnings, impressions, clicks, and ad performance.

Instructions

Generate a detailed AdSense performance report with custom dimensions and metrics

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "adsense_generate_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return (default: 100, max: 10000)
endDateNoEnd date (YYYY-MM-DD). Defaults to yesterday.
filtersNoFilters as DIMENSION==value (exact match) or DIMENSION=@value (contains), e.g. COUNTRY_CODE==US. Separate entries are ANDed; use a comma inside one entry for OR (COUNTRY_CODE==US,COUNTRY_CODE==GB). Date dimensions cannot be filtered.
metricsNoMetrics to include, such as ESTIMATED_EARNINGS, IMPRESSIONS, CLICKS, PAGE_VIEWS, PAGE_VIEWS_RPM, AD_REQUESTS, and AD_REQUESTS_COVERAGE.
orderByNoDimension or metric to sort by. Prefix with - for descending or + for ascending, e.g. -ESTIMATED_EARNINGS.
accountIdNoAdSense account ID. Uses default if not specified.
startDateNoStart date (YYYY-MM-DD). Defaults to 7 days ago.
dimensionsNoDimensions to group by. For country/platform reports use COUNTRY_NAME or COUNTRY_CODE with PLATFORM_TYPE_CODE or PLATFORM_TYPE_NAME. For custom channel reports use CUSTOM_CHANNEL_NAME or CUSTOM_CHANNEL_ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses almost nothing beyond the output being a "detailed" report. It never states that this is a read-only query, that startDate defaults to 7 days ago and endDate to yesterday, that rows are capped at 100 by default, or what the returned structure looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single tight sentence with no wasted words, front-loading the action and resource. It is efficient, though the brevity comes at the cost of the guidance and behavioral detail an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an eight-parameter reporting tool with no annotations and no output schema, the description is thin. It omits the default date window, row limits and pagination behavior, and account selection semantics, leaving the agent to discover core call behavior from the schema alone.

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% and all eight parameters are documented with enums, defaults, and filter syntax, so the schema does the heavy lifting. The description only restates that dimensions and metrics are custom, adding no syntax or semantic detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ("Generate a detailed AdSense performance report") and adds scope ("with custom dimensions and metrics"), so an agent knows this is the flexible reporting tool. It does not explicitly differentiate itself from siblings such as adsense_earnings_summary or adsense_compare_periods.

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?

Usage is only implied: the mention of "custom dimensions and metrics" hints this is the tool for arbitrary breakdowns, but the description never states when to prefer it over adsense_earnings_summary or adsense_compare_periods, nor any prerequisites like a required account or date range.

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