Skip to main content
Glama
Sign In
AdMob MCP

AdMob MCP

by jimsimoy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_apps

List all apps associated with a specific AdMob publisher account using the account ID.

Instructions

List apps under an account. account_name looks like 'accounts/pub-1234567890123456'.

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": {
      "account_name": "<account_name>"
    },
    "name": "list_apps"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states the operation is a list (read-only) and gives the account_name format, which is useful. However, it does not disclose pagination, ordering, or any other behavioral details. For a simple read operation, this is acceptable but minimal.

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?

The description is two short sentences with no filler. The key scope ('under an account') is front-loaded, and the parameter format is provided succinctly. Every word earns its place.

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?

The tool has an output schema, so return values are covered. The description is sufficient for a simple list operation with one parameter, given the sibling context. It could mention pagination or sorting, but those are minor for this use case.

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 coverage is 0%, so the description must compensate. It does so by specifying the expected format of account_name ('accounts/pub-1234567890123456'), which adds meaningful guidance beyond the bare string type in the schema. This fully clarifies the single parameter.

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 lists apps under an account, with a specific resource and scope. It is distinct from siblings like list_accounts (accounts) and get_account (single account), so an agent can easily tell it apart.

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?

There is no explicit guidance on when to use this tool versus alternatives. The description implies it is for listing apps, but does not mention when not to use it or how it differs from list_accounts or list_ad_units. The agent must infer usage from the name and context.

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