Skip to main content
Glama
flin-google-ads-mcp

flin-google-ads-mcp

by flin-agency

get_ads

Read-only

Retrieve ads for a Google Ads customer account, optionally filtered by campaign or ad group, to inspect ad details and status without modifying account data.

Instructions

Get ads for a customer account, optionally filtered by campaign or ad group.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
statusNoALL
ad_group_idNo
campaign_idNo
customer_idNo
login_customer_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds no further behavior – no pagination behavior, no note that status defaults to 'ALL' or limit defaults to 50, and no mention that an unfiltered call returns everything in the account. It essentially restates the filtering parameters.

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?

One front-loaded sentence with zero filler, and filtering scope is stated immediately. It is efficient, though the terseness is part of why parameter meaning is missing.

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

Completeness2/5

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

An output schema exists, so return values need not be described, but with six undocumented parameters, no required field, and no guidance on defaults like limit=50 or status='ALL', the agent lacks what it needs to call this correctly. A sentence on paging and on the login_customer_id/MCC distinction would close most of the gap.

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% across six parameters, so the description carries the burden and largely fails: it touches campaign_id and ad_group_id only vaguely and says nothing about limit, status, login_customer_id, or why customer_id is nullable despite the 'for a customer account' framing. Half the parameters remain unexplained in both schema and prose.

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 pairs a specific verb with a specific resource ('Get ads for a customer account'), which reads clearly against siblings such as get_ad_groups and get_campaigns. It stops just short of an explicit differentiation sentence, but the resource noun alone is unambiguous.

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?

'Optionally filtered by campaign or ad group' implies how the tool is scoped, but it never states when an agent should call get_ads versus get_ad_groups/get_campaigns, nor what happens if no filter is supplied. Usage is inferable rather than prescribed.

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