Skip to main content
Glama

google_ads_schedule_targeting_list

List ad-schedule targeting criteria for a Google Ads campaign. Returns day-of-week, hour ranges, and bid modifier per criterion. Use to audit schedule coverage or collect IDs before updating.

Instructions

List the ad-schedule (day-of-week + hour-of-day) targeting criteria attached to a Google Ads campaign. Returns one row per schedule criterion with criterion_id (string), day_of_week (string form of the DayOfWeek enum, e.g. 'MONDAY'..'SUNDAY'), start_hour (integer 0-23), end_hour (integer 0-24; 24 denotes end-of-day), start_minute and end_minute (string form of the MinuteOfHour enum: 'ZERO', 'FIFTEEN', 'THIRTY', or 'FORTY_FIVE'), and bid_modifier (float, or null when unset). Read-only; returns an empty list when the campaign has no schedule targeting (meaning: 24/7 delivery). Use this to audit schedule coverage or collect criterion_ids before calling google_ads_schedule_targeting_update (which is what you use to add or remove entries). For device-level modifiers use google_ads_device_targeting_get; for geo targeting use google_ads_location_targeting_list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
campaign_idYesCampaign ID as a numeric string (e.g. '23743184133'). Required — schedule targeting is always scoped to a single campaign. Obtain via google_ads_campaigns_list.
Behavior5/5

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

With no annotations, the description fully discloses read-only behavior, empty list semantics for 24/7 delivery, and the exact output structure. No contradictions.

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?

The description is thorough but efficient, delivering all needed information in 3-4 sentences. It is front-loaded with the main purpose and returns structure. Could be slightly shorter but no wasted words.

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?

For a list operation with only 2 params and no output schema, the description is complete: it explains inputs, outputs, edge cases (empty list), and how it fits with sibling tools.

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 is 100%, and the description adds useful context: customer_id is optional with fallback to credentials, campaign_id is required and obtainable via google_ads_campaigns_list. This goes beyond the schema.

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 it lists ad-schedule targeting criteria, specifying the return fields (criterion_id, day_of_week, et al.) and that it is read-only. It distinguishes from sibling tools like google_ads_schedule_targeting_update, google_ads_device_targeting_get, and google_ads_location_targeting_list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to use for auditing schedule coverage or collecting criterion_ids before calling the update tool. Provides when-not-to-use (returns empty for 24/7 delivery) and directs to alternative tools for device and geo targeting.

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