Skip to main content
Glama

MetricPort

AdSense earnings

adsense_earnings
Read-onlyIdempotent

Earnings summary: totals for the range (default last 30 days) plus a daily breakdown. compare=true adds the previous period with percentage change.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "property": "<property>"
    },
    "name": "adsense_earnings"
  }
}

Input Schema

NameRequiredDescriptionDefault
compareNo
endDateNo
propertyYesAdSense account id from list_properties, e.g. accounts/pub-1234567890123456
startDateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the read-only, idempotent, non-destructive profile, and the description adds real context on top: the default range (last 30 days), the output shape (totals + daily breakdown), and the exact effect of compare (adds previous period with percentage change). It still says nothing about account/property authorization requirements or result volume, but it clears the annotation-adjusted bar.

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 sentences, front-loaded with what is returned, then the optional compare behavior. No filler; each clause carries information an agent needs.

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?

With no output schema, the description usefully describes the return shape (range totals plus daily breakdown) and the compare variant. Remaining gaps are minor: no mention of account scoping via list_properties or date-format expectations, both partly inferable from siblings and the schema pattern.

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 only 25% (property alone is documented), so the description must compensate; it does cover compare and the default date window that governs startDate/endDate. However, it adds nothing about the required property parameter, its list_properties source, or the YYYY-MM-DD date format, leaving date semantics thin.

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?

States a specific resource (AdSense earnings) and precise scope: range totals plus a daily breakdown. An agent can tell it returns an earnings summary with daily granularity, though it never distinguishes itself from near-siblings like adsense_report, adsense_daily_trend, or adsense_monthly_report.

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 rather than stated: the default 30-day window and the compare=true period-over-period mode sketch the intended scenarios. No explicit when-not or alternative tool is named, so an agent facing the earnings/report/daily-trend cluster gets no routing help.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.