Skip to main content
Glama
AdSense-MCP-Server

AdSense-MCP-Server

by AppsYogi-com

adsense_earnings_summary

Retrieve a quick AdSense earnings summary for today, yesterday, the last 7 days, this month, and last month; optionally specify an account ID or use the default.

Instructions

Get a quick earnings summary (today, yesterday, last 7 days, this month, last month)

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

Input Schema

NameRequiredDescriptionDefault
accountIdNoAdSense account ID (e.g., pub-1234567890123456). Uses default if not specified.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It conveys that the tool is a read-style summary over fixed periods, but says nothing about currency, timezone, aggregation method, data freshness, or response shape, which matter for interpreting earnings figures.

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 definition is a single front-loaded sentence with the resource first and the supported windows in a compact parenthetical. Every element earns its place with no redundant wording.

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 simple, zero-required-parameter summary tool with no output schema, the description sufficiently conveys what periods are covered and that results are a quick summary. Minor gaps around currency, timezone, and comparison against sibling reporting tools keep it from being fully complete.

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?

There is a single optional accountId parameter, and the schema already documents its format and default behavior at 100% coverage. The description adds no further meaning about accountId, so the baseline of 3 is appropriate.

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 states a specific verb and resource ("Get a quick earnings summary") and enumerates the exact time windows covered (today, yesterday, last 7 days, this month, last month). This lets an agent distinguish it from siblings like adsense_compare_periods or adsense_generate_report, though it does not name those alternatives explicitly.

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 implied by "quick earnings summary" over fixed rolling windows, suggesting a lightweight overview call. However, there is no explicit statement of when to prefer this over adsense_compare_periods, adsense_generate_report, or adsense_export_csv, and no exclusions or prerequisites are given.

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