Skip to main content
Glama
kLOsk

AdLoop: Google Ads, Reddit Ads & GA4

by kLOsk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Demographic targeting

get_demographic_targeting
Read-only

List age, gender, parental status, and income targeting criteria for a Google Ads ad group or campaign to check exclusions, narrowing status, and removal IDs.

Instructions

List demographic targeting criteria (age, gender, parental status, income).

Takes exactly one of ad_group_id or campaign_id. Returns each criterion's value, whether it's negative (excluded) or positive (narrowing), status, and a remove_id (composite resource ID) that can be passed directly to remove_entity with entity_type='ad_group_criterion' or 'campaign_criterion'.

By default, Google Ads serves ads to ALL demographic segments — a criterion only appears here once a segment has been actively excluded or narrowed.

Google Ads API: https://developers.google.com/google-ads/api/docs/start

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ad_group_idNoNumeric ad group ID. Mutually exclusive with campaign_id.
campaign_idNoNumeric campaign ID. Mutually exclusive with ad_group_id.
customer_idNoGoogle Ads customer ID, digits with or without dashes (e.g. "123-456-7890"). Defaults to the configured ads.customer_id.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.27.1
    • addedInput schema / properties / ad_group_id / description
      Added value: +"Numeric ad group ID. Mutually exclusive with campaign_id."
    • addedInput schema / properties / campaign_id / description
      Added value: +"Numeric campaign ID. Mutually exclusive with ad_group_id."
    • addedInput schema / properties / customer_id / description
      Added value: +"Google Ads customer ID, digits with or without dashes\n(e.g. \"123-456-7890\"). Defaults to the configured ads.customer_id."
  2. Addedv0.12.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover read-only/safe/open-world, but the description adds genuinely new behavior: the default 'serves ads to ALL demographic segments' model and the fact that a criterion only materializes after exclusion or narrowing. It also describes return content (value, negative vs positive, status, remove_id) and the composite-ID handoff to remove_entity, none of which annotations convey.

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?

Front-loaded with the purpose, then parameter constraint, then return contract, then the important default-behavior caveat. Slightly redundant in re-explaining mutual exclusivity already in the schema, but every sentence carries useful weight.

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?

An output schema exists, yet the description still correctly summarizes the salient return fields and the cross-tool remove_id workflow. Combined with full schema coverage and annotations, an agent has everything needed to call and act on results.

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 100%, so mutual exclusivity and IDs are already documented. The description restates the one-of constraint and adds the Google Ads default-behavior nuance, but adds no format details beyond the schema, so the baseline of 3 applies.

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?

Specific verb (List) plus the exact resource and its enumerated segments (age, gender, parental status, income). An agent can immediately distinguish this read tool from sibling draft_demographic_targeting without opening either schema.

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?

States the 'exactly one of ad_group_id or campaign_id' selection rule and explains that a criterion only appears once it has been actively excluded or narrowed, which sets expectations for when the tool returns meaningful data. It also routes the agent onward (remove_id → remove_entity). It stops short of naming alternatives like draft_demographic_targeting explicitly.

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

Deploy Server

Other Tools