Skip to main content
Glama
AdSense-MCP-Server

AdSense-MCP-Server

by AppsYogi-com

adsense_list_accounts

Lists every Google AdSense account you can access, so you can identify the correct account before running earnings reports or site status checks.

Instructions

List all AdSense accounts you have access to

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key scope constraint that results are limited to accounts the caller can access. It stops short of stating that this is a non-destructive read with no pagination or filtering, which matters for a list operation.

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?

One short sentence with zero filler and the scope qualifier front-loaded at the end of the phrase where it belongs. It is efficient, though it offers no second sentence of routing or behavior detail.

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 zero-parameter, no-output-schema list tool, the definition covers what the tool returns conceptually (all accessible accounts). The only remaining gap is return shape and whether results are paginated, which is minor at this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The single sentence does not need to explain any parameter meaning.

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?

"List all AdSense accounts you have access to" states a specific verb (List) and resource (AdSense accounts) directly. It is clearly distinguishable from siblings like adsense_list_ad_units or adsense_list_payments by resource alone, though it never names an alternative 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 only implied by the verb: call this when you need the account inventory. There is no statement of when not to use it, prerequisites, or a pointer to alternatives such as adsense_earnings_summary for account-level data.

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