Skip to main content
Glama
AdSense-MCP-Server

AdSense-MCP-Server

by AppsYogi-com

adsense_list_policy_issues

List AdSense policy issues and violations for an account to spot warnings, ad-serving restrictions, or disabled ad serving.

Instructions

List policy issues and violations affecting your account (WARNED, AD_SERVING_RESTRICTED, AD_SERVING_DISABLED)

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

Input Schema

NameRequiredDescriptionDefault
accountIdNoAdSense account ID. Uses default if not specified.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the policy-state values that will appear in results, which is useful behavioral content, but it says nothing about permissions, rate limits, result ordering, or whether the listing is paginated or complete.

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?

One sentence with zero filler: the verb, the resource, the scope, and the state enumeration are all front-loaded. Nothing could be removed without losing information.

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?

For a read-only list tool with one optional parameter and no output schema, the definition covers what is needed to select and call it. It leaves the exact return fields unspecified, but the enumerated states give a reasonable picture of the response.

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% and the single optional accountId parameter is already documented as falling back to a default. The description adds no meaning beyond the schema, so the baseline 3 applies.

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 uses a specific verb plus resource ("List policy issues and violations") and enumerates the states returned (WARNED, AD_SERVING_RESTRICTED, AD_SERVING_DISABLED), which makes it distinctive from sibling list tools such as adsense_list_alerts. It stops short of explicitly differentiating itself from those siblings, so not a 5.

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?

Usage is only implied: "affecting your account" suggests this is the tool for checking account health, and the parenthetical states hint at the triage use case. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g., adsense_list_alerts) to route between them.

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