admob-mcp

by jerry2247

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

List ad source adapters

admob_list_adapters

Read-only

List adapters for an ad source to retrieve adapter IDs and config metadata required for ad unit mapping creation.

Instructions

List the adapters for one ad source. An adapter is a platform-specific SDK implementation; its adapterId and adapterConfigMetadata are needed to create ad unit mappings.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "adSourceId": "<adSourceId>"
    },
    "name": "admob_list_adapters"
  }
}

Input Schema

Name	Required	Description
`pageSize`	No
`pageToken`	No
`adSourceId`	Yes	The ad source id (from admob_list_ad_sources).
`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.2/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=true, and the description confirms a read operation. It adds behavioral context by explaining the output's role in creating mappings, which is beyond the 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?

Two sentences with no wasted words, front-loading the core purpose and then adding necessary explanatory context.

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?

Lacks output schema but the description explains what the output contains. Annotations cover safety. Could be more explicit about the list format but sufficient for the task.

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 50% (2 of 4 parameters described). The description does not add extra parameter meaning beyond the schema; it focuses on output behavior. Baseline of 3 is appropriate.

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 'List the adapters for one ad source' with a specific verb and resource. It explains the purpose of adapters and distinguishes this tool from siblings by focusing on adapter listing.

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 when to use (to get adapterId and adapterConfigMetadata for creating mappings) and provides context but does not explicitly list when not to use it or alternative tools.

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