Skip to main content
Glama
AdSense-MCP-Server

AdSense-MCP-Server

by AppsYogi-com

adsense_compare_periods

Compare AdSense performance between two date ranges to spot trends and quantify changes in earnings, impressions, and other metrics.

Instructions

Compare AdSense performance between two time periods

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": {
      "period1Start": "<period1Start>",
      "period1End": "<period1End>",
      "period2Start": "<period2Start>",
      "period2End": "<period2End>"
    },
    "name": "adsense_compare_periods"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountIdNoAdSense account ID. Uses default if not specified.
dimensionsNoDimensions to group by for comparison, e.g. COUNTRY_NAME, PLATFORM_TYPE_CODE, or CUSTOM_CHANNEL_NAME.
period1EndYesFirst period end date (YYYY-MM-DD)
period2EndYesSecond period end date (YYYY-MM-DD)
period1StartYesFirst period start date (YYYY-MM-DD)
period2StartYesSecond period start date (YYYY-MM-DD)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does not meet it. It says nothing about which metrics are compared (earnings, impressions, CTR, RPM), how the comparison is presented (delta, percent change, side-by-side), or whether it is a read-only query with any rate or quota limits.

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 short sentence with no filler, front-loading the action and scope. Its brevity is efficient, though it edges toward under-specification rather than tightness.

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?

This is a moderately complex analytical tool with four required date parameters, an optional grouping dimension, no output schema, and no annotations. One sentence cannot cover what the comparison returns or how periods must relate, so an agent would have to guess at the result shape and validity constraints.

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 all six parameters are already documented with types, formats (YYYY-MM-DD), and a large dimension enum list. The description adds no meaning beyond the schema — it does not explain how the dimension choice affects the comparison output. Baseline 3 applies when the schema does the heavy lifting.

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 ('Compare') and resource ('AdSense performance') and states the scope ('between two time periods'), which distinguishes it from single-period siblings like adsense_earnings_summary. It stops short of explicitly naming which sibling to use for non-comparative reporting, so it is clear but not fully differentiated.

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?

There is no explicit when-to-use or when-not-to-use guidance. The description does not tell the agent how this differs from adsense_generate_report or adsense_earnings_summary, nor does it state constraints such as whether the two periods must be equal length or non-overlapping.

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