Skip to main content
Glama
Sign In
admob-mcp

admob-mcp

by jerry2247
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List ad unit mappings

admob_list_ad_unit_mappings
Read-only

List all ad unit mappings for a given AdMob ad unit to view the mediation and ad source settings applied.

Instructions

List the ad unit mappings under one ad unit.

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": {
      "adUnitId": "<adUnitId>"
    },
    "name": "admob_list_ad_unit_mappings"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNo
adUnitIdYesThe ad unit id (numeric portion or full id).
pageSizeNo
pageTokenNo
publisherIdNoAdMob 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.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations indicate readOnlyHint=true and openWorldHint=true, which convey safety and potential large results. The description does not add behavioral details like pagination behavior, authorization needs, or rate limits. Minimal value beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence without wasted words. However, it is too terse, lacking necessary detail for a tool with multiple parameters. Not excessively long, but under-specified.

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

Completeness2/5

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

Given the complexity (5 parameters, list operation, pagination), the description is incomplete. It does not explain pagination, sorting, or filtering. The absence of an output schema increases the need for description content, which is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 40% (2 of 5 parameters have descriptions). The tool description does not elaborate on any parameters. It does not compensate for the low schema coverage, leaving parameters like 'all', 'pageSize', 'pageToken' unexplained.

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

Purpose4/5

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

The description clearly states the verb 'List', the resource 'ad unit mappings', and the scope 'under one ad unit'. It distinguishes from create/batch siblings, though not explicitly. The purpose is specific and not a tautology.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like admob_create_ad_unit_mapping. No mention of prerequisites, context, or when not to use. The description is purely declarative.

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

Deploy Server

Other Tools