Skip to main content
Glama

google_ads_schedule_targeting_list

Retrieve day-of-week and hour-of-day ad schedule targeting criteria for a Google Ads campaign. Audit schedule coverage or collect criterion IDs before updates. Read-only list; returns empty for 24/7 delivery.

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
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.
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?

With no annotations provided, the description carries the full burden. It discloses read-only behavior ('Read-only'), return semantics ('returns an empty list when the campaign has no schedule targeting (meaning: 24/7 delivery)'), and details each return field with types and enum ranges. This is comprehensive behavioral disclosure beyond what a schema could provide.

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?

The description is detailed but every sentence adds value: the main action, return field specification, edge-case behavior, and cross-references to related tools. It is front-loaded with the primary purpose and structured logically without unnecessary filler.

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?

Without an output schema, the description fully documents the return shape including criterion_id, day_of_week, start_hour, end_hour, start_minute, end_minute, and bid_modifier, plus edge cases like empty list and null bid_modifier. It also contextualizes usage within the broader targeting toolset, making it complete for an agent to invoke correctly.

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?

The input schema has 100% description coverage for both campaign_id and customer_id, so the schema already explains the parameters. The description adds context around the update workflow but does not add new parameter-level semantics beyond what the schema provides. Baseline 3 is appropriate.

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 opens with a specific verb+resource: 'List the ad-schedule (day-of-week + hour-of-day) targeting criteria attached to a Google Ads campaign.' This clearly identifies what the tool does and distinguishes it from sibling tools like google_ads_schedule_targeting_update and google_ads_device_targeting_get.

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?

The description explicitly states when to use this tool: 'Use this to audit schedule coverage or collect criterion_ids before calling google_ads_schedule_targeting_update.' It also mentions the alternative for device modifiers and geo targeting, providing clear when-to-use versus when-not-to-use guidance.

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