Skip to main content
Glama
Sign In
Hexagon MCP

Hexagon MCP

by smallware-co
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

adsense_report

Query AdSense performance read-only to retrieve earnings, page views, impressions, clicks, and CTR by day using presets or custom dates; defaults to the last 7 days.

Instructions

Query AdSense performance (read-only). Defaults to earnings, page views, impressions, clicks and CTR by day for the last 7 days.

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_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows. Default 50.
endDateNoYYYY-MM-DD, use together with startDate.
metricsNoDefault: ESTIMATED_EARNINGS, PAGE_VIEWS, IMPRESSIONS, CLICKS, IMPRESSIONS_CTR. Also PAGE_VIEWS_RPM, COST_PER_CLICK.
dateRangeNoPreset range. Default: LAST_7_DAYS. Ignored when startDate and endDate are both given.
startDateNoYYYY-MM-DD, use together with endDate.
dimensionsNoDefault: ['DATE']. Others: DOMAIN_NAME, COUNTRY_NAME, PLATFORM_TYPE_NAME, AD_UNIT_NAME, MONTH.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the read-only nature and the default window/breakdown (last 7 days, by day), but says nothing about authentication, quota/rate limits, the 1000-row cap's implications, or what the response payload 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.

Conciseness5/5

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

Two short sentences, front-loaded with the operation and safety profile, followed by the default output shape. Nothing is padded and the most important information comes first.

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 zero-required-parameter reporting tool with no output schema, the description gives the agent enough to call it blind: what it returns and what defaults will apply. The remaining gap is response shape/auth context, which a fourth sentence could have covered.

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 coverage is 100%, so every parameter is already documented, including defaults, enums, and the startDate/endDate interplay. The description merely restates the default metrics and 7-day default, adding no syntax or precedence detail beyond the schema; baseline 3 applies.

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?

"Query AdSense performance" states a specific verb and resource, and the source (AdSense) implicitly separates it from gsc_query and ga4_report. It stops short of explicitly naming those siblings, so the differentiation is inferred rather than stated.

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 by the source name and the "(read-only)" tag. There is no explicit when-to-use vs. when-to-use-ga4_report guidance, nor any statement of prerequisites such as a linked AdSense account.

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

Deploy Server

Other Tools