Skip to main content
Glama
OrbiAds

OrbiAds

Official

orders

Perform non-lifecycle order operations: list, get, create, update, archive, approve, and verify setup in Google Ad Manager.

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, secondarySalespersonIds, traffickerId, customFieldValues, 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

TableJSON Schema
NameRequiredDescriptionDefault
actionYesSub-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, salespersonId, secondarySalespersonIds, customFieldValues, 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.
order_idNoGAM Order ID (required for single-entity operations).
network_codeNoGAM network code (e.g. 12345678). Required for all network-scoped operations. Obtain via select_gam_network or list_accessible_networks.
Behavior5/5

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

With no annotations, the description fully covers behavioral traits: MODE (mixed), AUTH (OAuth 2.0 required), CREDITS (reads 0, writes 0.5), and OUTPUT fields. It also flags destructive actions (archive) and idempotency (find_or_create), providing comprehensive behavioral context beyond what structured fields would offer.

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 well-structured with clear sections (purpose, mode/auth/credits/output, usage guidance, differentiation). It is informative without being overly verbose, though slightly long. Every sentence earns its place, and key info is front-loaded.

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?

Given the tool's complexity (11 sub-actions), absence of output schema, and no annotations, the description compensates well. It details each action, output fields, and usage context, making it complete for an agent to understand and use correctly.

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%, so baseline is 3. The description adds meaningful context for the 'action' parameter by detailing each enum value with read/write status and requirements (e.g., 'create: Write. Requires advertiserId, name, and traffickerId'). This enhances understanding beyond the schema descriptions.

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 the tool's purpose as 'Non-lifecycle Order operations — list, get, create, update, and manage orders.' It differentiates from sibling tools like campaign and order_lifecycle with explicit statements, making the purpose distinct and well-defined.

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 'WHEN TO USE' section explicitly states when to use this tool ('Use orders for Order entity management') and when not to, naming alternatives ('Use campaign for full campaign orchestration... Use order_lifecycle for status transitions'). This provides clear guidance for an AI agent.

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/OrbiAds/Orbiads-GAM-MCP'

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