Skip to main content
Glama
Sign In

Google Ads

by io.github.mcp-dir
OverviewDiscussionsAdmin

google_ads_ads

Read-onlyIdempotent

List enabled ads with type, status, campaign name and ad_group_ad.policy_summary (approval_status, review_status, policy_topic_entries) — answers "why is my ad not serving?" without opening the Google Ads UI.

Bulk support: accepts customer_ids for batched execution.

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

Input Schema

NameRequiredDescriptionDefault
accountNo
customer_idNo
customer_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful behavioral context beyond those hints, including the specific policy_summary fields returned and the ability to execute against multiple customer_ids in bulk. No contradictions 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?

The description is compact and front-loaded, with the first sentence stating what the tool does and what it returns. The second sentence adds a distinct bulk-execution capability. Every sentence adds value with no filler.

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 simple read-only listing tool with no output schema, the description covers the tool's purpose, returned fields, a motivating use case, and bulk behavior. The main gap is the unresolved semantics of account and customer_id, but overall the description is sufficiently complete for most selection and invocation scenarios.

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 0%, so the description must compensate for parameter meaning. It only explains customer_ids as providing bulk execution; the purpose and relationship of 'account' and 'customer_id' are left unspecified. This is insufficient for fully guiding an agent on how to supply parameters.

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 uses a specific verb and resource: 'List enabled ads' followed by the exact fields returned (type, status, campaign name, policy_summary details). It clearly distinguishes this from sibling tools like google_ads_campaigns or google_ads_keywords by focusing on ads and their policy approval/review status.

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 gives a concrete use case: answering 'why is my ad not serving?' without opening the Google Ads UI. It also notes bulk support via customer_ids. It does not explicitly mention when not to use the tool or name alternatives, but the context is clear enough for an agent to select it over related read/write ad tools.

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

All Google Ads toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources