admob-mcp

Overview Schema Source Related Servers Discussions Admin

Update mediation group

admob_update_mediation_group

DestructiveIdempotent

Update an AdMob mediation group by specifying changed fields with a field mask. Optionally validate the request before execution.

Instructions

Update a mediation group (v1beta patch, allowlisted). updateMask is required and selects which fields change; repeated fields are fully replaced. See the AdMob docs for supported field mask paths.

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": {
      "mediationGroupId": "<mediationGroupId>",
      "updateMask": "<updateMask>",
      "mediationGroup": "<mediationGroup>"
    },
    "name": "admob_update_mediation_group"
  }
}

Input Schema

Name	Required	Description
`dryRun`	No	If true, validate the inputs and return the exact API request that would be sent WITHOUT executing it. Default false: the operation runs after the MCP client asks you to confirm.
`updateMask`	Yes	Comma-separated FieldMask of fields to update, e.g. "display_name,targeting.ad_unit_ids".
`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.
`mediationGroup`	Yes	Partial MediationGroup with the fields to update.
`mediationGroupId`	Yes

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 provide readOnlyHint=false, destructiveHint=true, idempotentHint=true. The description adds useful context: it's a patch operation, updateMask is required, repeated fields are fully replaced, and it's 'allowlisted'. No contradiction with 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 without redundancy. The first sentence states the purpose immediately. Every part adds value: method, updateMask requirement, replacement behavior, and reference to docs for mask paths.

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?

Given the tool has 5 parameters, high schema coverage, and annotations covering safety, the description is adequately complete. It explains key behavioral aspects (updateMask, repeated fields) but omits return value info (no output schema) and prerequisites, though these are partially covered by schema and context.

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

Parameters4/5

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

Schema description coverage is 80%, providing decent baseline. The description adds value by explaining updateMask behavior (required, selects fields, repeated fields replaced) beyond the schema's example. This helps the agent understand the parameter semantics.

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 the tool updates a mediation group, specifies it uses v1beta patch, and distinguishes from create_mediation_group sibling. The verb 'update' and resource 'mediation group' are explicit.

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

Usage Guidelines3/5

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

The description implies usage for updating mediation groups but does not provide explicit guidance on when to use versus alternatives like create_mediation_group. No when-not-to-use or prerequisite information is given.

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