admob-mcp

by jerry2247

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Get AdMob account

admob_get_account

Read-only

Get details for an AdMob publisher account, including publisher ID, reporting time zone, and currency code.

Instructions

Get details for one AdMob publisher account (publisher id, reporting time zone, currency code).

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": "admob_get_account"
  }
}

Input Schema

Name	Required	Description	Default
`publisherId`	No	AdMob publisher id or account resource name, e.g. "pub-1234567890123456" or "accounts/pub-1234567890123456". Defaults to ADMOB_PUBLISHER_ID, or the single account on the credentials.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds value by specifying the exact details returned (publisher id, time zone, currency code). No contradictions; it could mention error handling but is sufficient given annotations.

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?

A single sentence, 16 words, that efficiently conveys purpose and output without waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has one optional parameter, readOnly and openWorld annotations, and no output schema, the description is complete enough for an agent to understand its use and output.

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%, so baseline is 3. The description repeats some fields returned but does not add meaning beyond the schema's parameter description for publisherId.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it 'Get details for one AdMob publisher account' and lists specific fields returned (publisher id, time zone, currency code). This distinguishes it from sibling tool admob_list_accounts which lists multiple accounts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for retrieving a single account, and the presence of admob_list_accounts as a sibling suggests when to use each. However, no explicit when-not-to-use or alternatives are given, though context is clear.

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