Skip to main content
Glama
AdSense-MCP-Server

AdSense-MCP-Server

by AppsYogi-com

adsense_list_payments

Retrieve AdSense payment history and pending earnings for an account to track past payouts and upcoming balances. Specify an account ID or use the default account.

Instructions

List payment history and pending earnings

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

Input Schema

NameRequiredDescriptionDefault
accountIdNoAdSense account ID. Uses default if not specified.

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 provided, so the description carries the full behavioral burden. It implies a safe read via 'List' but says nothing about pagination, date-range defaults, whether pending earnings require settlement delays, or permission requirements — real gaps for a financial data tool with zero annotation coverage.

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?

Six words, front-loaded with the verb and resource, zero filler. It is efficient but borders on under-specification given the absence of annotations and output schema.

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?

For a financial reporting tool with no annotations and no output schema, the description should at least indicate the shape or scope of returned payment records and the relationship to the earnings summary tool. It supplies only the topic, leaving the agent to guess at coverage and defaults.

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% and the single optional accountId parameter is fully documented in the schema, including the default-account fallback. The description adds no meaning beyond that, which is the expected baseline when the schema does the work.

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?

Specific verb 'List' plus two concrete resources: payment history and pending earnings. An agent knows what data comes back, though the description never distinguishes this from the sibling adsense_earnings_summary, which plausibly covers overlapping earnings 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?

No statement of when to use this versus adsense_earnings_summary, adsense_generate_report, or adsense_compare_periods, and no preconditions such as whether an account must exist. The only usage signal is the implicit 'list all payments' scope.

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