AdMob MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ADMOB_CLIENT_ID | Yes | OAuth client ID for the Google AdMob API | |
| ADMOB_CLIENT_SECRET | Yes | OAuth client secret for the Google AdMob API | |
| ADMOB_REFRESH_TOKEN | Yes | Refresh token obtained via interactive authorization |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_accountsA | List AdMob publisher accounts accessible to this credential. |
| get_accountA | Fetch one account's details. account_name looks like 'accounts/pub-1234567890123456'. |
| list_appsA | List apps under an account. account_name looks like 'accounts/pub-1234567890123456'. |
| list_ad_unitsB | List ad units under an account. account_name looks like 'accounts/pub-1234567890123456'. |
| generate_network_reportA | Generate an AdMob network (own ad serving) performance report. |
| generate_mediation_reportA | Generate an AdMob mediation performance report (earnings across ad sources). |
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 6 tools
Each tool maps to a distinct resource or action: accounts, apps, ad units, and two clearly differentiated report types (network vs. mediation). No meaningful overlap exists between tool purposes.
Tool names follow a consistent verb_noun pattern: list_accounts, get_account, list_apps, list_ad_units, generate_network_report, generate_mediation_report. The pattern is predictable and uniform.
Six tools is well-scoped for an AdMob read/reporting surface. Each tool earns its place without redundancy or bloat.
The surface covers account discovery, app/ad unit listing, and comprehensive network/mediation reporting. Minor gaps exist for detailed per-app or per-ad-unit lookups and mutation operations, but core reporting workflows are well covered.