adsense-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ADSENSE_CLIENT_ID | No | OAuth client ID. Must be used together with ADSENSE_CLIENT_SECRET and ADSENSE_REFRESH_TOKEN. | |
| ADSENSE_ACCESS_TOKEN | No | OAuth access token for AdSense Management API. Use this instead of the client ID/secret/refresh token combination. | |
| ADSENSE_CLIENT_SECRET | No | OAuth client secret. Must be used together with ADSENSE_CLIENT_ID and ADSENSE_REFRESH_TOKEN. | |
| ADSENSE_REFRESH_TOKEN | No | OAuth refresh token. Must be used together with ADSENSE_CLIENT_ID and ADSENSE_CLIENT_SECRET. |
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 |
|---|---|
| adsense_list_accountsA | List AdSense accounts available to the authenticated user. |
| adsense_get_accountA | Get one AdSense account by resource name, e.g. accounts/pub-123. |
| adsense_generate_reportA | Extract any ad-hoc AdSense report. Supply API v2 dimensions, metrics, filters, dates, sorting, and other report parameters. Account is discovered automatically when omitted. |
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 3 tools
Each tool targets a distinct operation: listing accounts, retrieving a specific account, and generating reports. There is no overlap between these actions, and the report tool even auto-discovers the account, reducing ambiguity.
All tool names follow a consistent verb_noun pattern with the 'adsense_' prefix (list_accounts, get_account, generate_report). This makes the naming predictable and easy to navigate.
With 3 tools, the server is on the lower end of the ideal range, but it covers the core AdSense operations: account listing, account retrieval, and report generation. The count feels minimal yet sufficient for a focused server, though slightly thin.
The surface covers essential account and reporting operations, but lacks other common AdSense resources like ad units, sites, or alerts. This might be a notable gap for agents needing broader management capabilities, though it may be acceptable for a report-focused server.