Skip to main content
Glama
davidmosiah

Google Ads MCP Unofficial

List Google Ads Keywords

google_ads_list_keywords
Read-onlyIdempotent

List keyword criteria under a Google Ads campaign or ad group. Returns keyword text, match type, status, and CPC bid.

Instructions

List keyword criteria under a campaign or ad group. Returns criterion_id, keyword text, match type, status, and cpc_bid_micros.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoENABLED
page_sizeNo
ad_group_idNoOptional ad group id filter.
campaign_idNoOptional campaign id filter.
customer_idYesGoogle Ads customer id (10 digits). Dashes optional, e.g. '1234567890' or '123-456-7890'.
privacy_modeNoOptional per-call payload privacy override. Defaults to GOOGLE_ADS_PRIVACY_MODE or structured.
response_formatNomarkdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNo
countNo
errorNo
recordsNo
has_moreNo
privacy_modeNo
next_page_tokenNo
Behavior3/5

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

Annotations declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds that it returns specific fields, which is useful but minimal 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.

Conciseness4/5

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

Single sentence that is efficient and front-loaded. Minimal waste, but could be slightly more structured.

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

Completeness3/5

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

With an output schema and return fields mentioned, the description covers core functionality. However, it omits pagination behavior, error handling, or prerequisites, which a complete description might include.

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 description coverage is 57%; the description does not add any extra meaning beyond the schema. Parameters are adequately documented in the schema itself, so this is a baseline score.

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 keyword criteria under a campaign or ad group, and specifies the return fields, distinguishing it from sibling tools like google_ads_list_ad_groups.

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 or when not to use it. The description lacks usage context entirely.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/davidmosiah/google-ads-mcp-unofficial'

If you have feedback or need assistance with the MCP directory API, please join our Discord server