adsense-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_accountsA | List all AdSense accounts associated with your Google account |
| list_ad_clientsA | List ad clients (publisher IDs) for an account |
| list_ad_unitsA | List all ad units. Returns name, displayName, state, type, and size for each unit. |
| create_ad_unitA | Create a new ad unit. Returns the created unit with its name and slot ID. |
| get_ad_codeB | Get the HTML/JS ad code snippet for an ad unit, ready to paste into your website |
| list_sitesA | List all sites in your AdSense account with their approval status and auto-ads setting |
| generate_reportA | Generate an AdSense earnings report with customizable date range, metrics, and dimensions |
| list_alertsA | List AdSense alerts and policy issues that need attention |
| list_paymentsA | List payment history for your AdSense account |
| generate_ads_txtA | Generate ads.txt content for your site. Place this file at your domain root (e.g., example.com/ads.txt). |
| verify_ads_txtB | Check if ads.txt is correctly set up on a domain by fetching and verifying its contents |
| get_ad_snippetB | Generate framework-specific ad integration code (React, Next.js, Vue, Astro, Svelte, etc.) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Most tools target clearly distinct resources and actions, such as listing accounts, creating ad units, and verifying ads.txt. The only potential confusion is between get_ad_code and get_ad_snippet, but their descriptions distinguish raw HTML/JS from framework-specific integration code.
Tool names consistently follow a verb_noun pattern in snake_case: list_*, create_ad_unit, get_ad_code, generate_report, verify_ads_txt. The naming is predictable and easy for an agent to navigate.
Twelve tools is well within the typical 3-15 range for a focused server. Each tool covers a meaningful AdSense workflow without obvious padding or duplication.
The server covers listing, creation, reporting, payments, alerts, and ads.txt verification, but has notable gaps: there is no update or delete operation for ad units, and site management is limited to listing. Agents can complete core workflows but cannot modify existing resources.