Skip to main content
Glama

google_ads_demographic_targeting_list

List explicit demographic criteria (age range, gender, parental status, household income) applied to Google Ads ad groups. Returns each criterion's type, value, status, and negative flag.

Instructions

Lists explicit demographic criteria (age range, gender, parental status, household income) set on ad groups. Returns one entry per criterion shaped {criterion_id, type ('AGE_RANGE'|'GENDER'|'PARENTAL_STATUS'|'INCOME_RANGE'), value (the segment enum, e.g. 'AGE_RANGE_25_34', 'FEMALE'), status, negative (true = excluded segment), campaign_id, ad_group_id, ad_group_name}. Read-only. Segments with no explicit criterion are targeted by default and do NOT appear — an empty result means 'all demographics, no exclusions', not 'nothing targeted'. Scope with ad_group_id and/or campaign_id, or omit both for the whole account (capped at 1000 criteria).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ad_group_idNoRestrict results to criteria on this ad group. Omit to read across the whole account (or scope with campaign_id).
campaign_idNoRestrict results to criteria under this campaign. Omit to read across the whole account.
customer_idNoGoogle Ads customer ID as a 10-digit string without dashes (e.g. '1234567890'). Optional — falls back to GOOGLE_ADS_CUSTOMER_ID / GOOGLE_ADS_LOGIN_CUSTOMER_ID from the configured credentials when omitted.
Behavior5/5

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

Discloses read-only nature, return shape with field examples, meaning of 'negative' flag, and that empty result means all demographics targeted. No annotations, so description fully carries load.

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?

Two packed sentences, front-loaded purpose, efficient. Every sentence adds value without redundancy.

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

Completeness5/5

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

Completely covers the tool's behavior for listing demographic criteria: return shape, scoping, empty result semantics, cap, and read-only nature. No gaps given the tool's simplicity.

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 100% but description adds scoping context for ad_group_id and campaign_id (scope with/omit). Customer_id handled by schema; description doesn't repeat its fallback behavior but that's acceptable as schema covers it.

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?

Clearly states it lists explicit demographic criteria (age range, gender, parental status, household income) on ad groups. Distinguishes from sibling 'google_ads_audience_targeting_list' by focusing on demographics.

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?

Provides clear guidance on scoping with ad_group_id/campaign_id or omitting for whole account, and explains empty result meaning. Does not explicitly list alternatives or when-not-to-use.

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/logly/mureo'

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