Skip to main content
Glama
AdSense-MCP-Server

AdSense-MCP-Server

by AppsYogi-com

adsense_export_csv

Exports AdSense report data as CSV, allowing you to specify date range, metrics, dimensions, and filters for custom reporting.

Instructions

Export AdSense report data as CSV format

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": {
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "adsense_export_csv"
  }
}

Input Schema

NameRequiredDescriptionDefault
endDateYesEnd date (YYYY-MM-DD)
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.
accountIdNoAdSense account ID. Uses default if not specified.
startDateYesStart date (YYYY-MM-DD)
dimensionsNoDimensions to include, e.g. COUNTRY_NAME, PLATFORM_TYPE_CODE, or CUSTOM_CHANNEL_NAME.

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 disclosure burden, and 'Export ... as CSV' is all it says. It does not state whether the result is a file path, a CSV string, or a download link, nor whether there are row limits, rate limits, or permission requirements for the default account. For a six-parameter exporting tool with zero annotation coverage this is a substantial gap.

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 front-loaded sentence with no filler, so nothing is wasted. Its brevity is close to under-specification rather than padding, which is a problem of completeness rather than structure.

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?

With six parameters, complex ANDed/ORed filter semantics, and no output schema, the description should at minimum explain the return shape and how it differs from adsense_generate_report. Neither is covered, leaving the agent to guess at the artifact it receives.

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%, including enum lists and a detailed filter syntax explanation, so the schema already does the parameter work. The description adds no meaning beyond it, which matches the baseline 3 for high-coverage schemas.

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 uses a specific verb and resource ('Export AdSense report data') and adds the output format ('CSV'), so the action is unmistakable. It does not, however, distinguish itself from the sibling adsense_generate_report, which an agent could reasonably assume also produces report data.

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 guidance on when to choose CSV export over adsense_generate_report or the summary/compare tools, and no stated prerequisites such as account selection or date-range limits. The agent must infer the choice from the name alone.

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