Skip to main content
Glama
AdSense-MCP-Server

AdSense-MCP-Server

by AppsYogi-com

adsense_list_sites

Lists all AdSense sites and their approval status (READY, GETTING_READY, NEEDS_ATTENTION, REQUIRES_REVIEW) to show which sites need attention; optionally filter by account ID.

Instructions

List all sites and their AdSense approval status (READY, GETTING_READY, NEEDS_ATTENTION, REQUIRES_REVIEW)

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

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

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does add real value by enumerating the four possible status values, telling the agent what to expect back, but it says nothing about read-only semantics, permission requirements, pagination, or whether results span one account or all.

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?

One sentence, front-loaded with the action and resource, with the status enum appended as useful detail. No filler or redundant restatement of the tool name.

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-required-parameter read/list tool with no output schema, the description covers what the tool returns at a level sufficient to call it correctly. It could still note pagination behavior or whether additional per-site fields are included, but the gaps are minor given the tool's simplicity.

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% and the single accountId parameter is fully documented in the schema, including its default behavior. The description adds no extra meaning about the parameter, so the baseline of 3 applies.

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 verb and resource ('List all sites') plus the exact payload dimension ('AdSense approval status'), which distinguishes it from sibling list tools such as adsense_list_accounts and adsense_list_ad_units by resource alone. It stops short of explicitly routing the agent away from any sibling, so it is clear but not maximally differentiating.

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: the agent can infer this is the tool for auditing which sites are approved or blocked. There is no statement of when to prefer it over a broader account listing, and no note about prerequisites such as needing an approved AdSense account.

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