orders
Manage Google Ad Manager orders: list, create, update, archive, approve, and verify setup. Retrieve order details and users. Supports read and write operations.
Instructions
Non-lifecycle Order operations — list, get, create, update, and manage orders.
MODE: mixed (read + write) AUTH: OAuth 2.0 required CREDITS: Reads = 0. Writes = 0.5 credits. OUTPUT: Returns Order objects with id, name, status, advertiserId, agencyId, salespersonId, traffickerId, totalBudget, and startDateTime/endDateTime. WHEN TO USE: Use orders for Order entity management. Use campaign for full campaign orchestration that includes Order + LineItems. Use order_lifecycle for status transitions. NOT the same as order_lifecycle: orders handles data; order_lifecycle handles approve/archive/disapprove transitions.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | Sub-operation to perform: • list_delivering: List orders currently in delivery. Read-only. • get: Get a single order by ID. Read-only. • list: List orders with optional filters (advertiser, status, date range). Read-only. • create: Create a new order. Write. Requires advertiserId, name, and traffickerId. • archive: Archive an order. Destructive write — stops delivery. • approve: Approve an order for delivery. Write. • verify_setup: Verify an order's setup (targeting, creative associations) before activation. Read-only. • update: Update an order's name, salesperson, or notes. Write. • find_or_create: Find an existing order matching the criteria or create a new one if not found. Idempotent write. • list_users: List users (salespeople, traffickers) associated with an order. Read-only. • list_roles: List available order roles. Read-only. | |
| network_code | No | GAM network code (e.g. 12345678). Required for all network-scoped operations. Obtain via select_gam_network or list_accessible_networks. | |
| order_id | No | GAM Order ID (required for single-entity operations). |