GAM REST Reporting

26 REST endpoints and MCP tools to create, run and manage GAM reports. Historical covers common AdOps use cases; the full catalogue serves as a validation dictionary.

REST endpoints

Method	Path	Description	Credits
POST	/reports/custom	Run a custom report (free dimensions + metrics)	0.5
POST	/reports/inventory	Run an inventory report	0.5
GET	/reports/available-dimensions	List the REST catalogue dimensions	0
GET	/reports/available-metrics	List the REST catalogue metrics	0
GET	/reports/available-date-ranges	List the relative date ranges	0
GET	/reports/templates	List templates (builtin + custom)	0
POST	/reports/templates	Create a custom template	0
POST	/reports/templates/{id}/run	Run a template	0.5
PUT	/reports/templates/{id}	Update a template	0
DELETE	/reports/templates/{id}	Delete a template	0
POST	/reports/templates/{id}/clone	Duplicate a template	0
POST	/reports/gam-reports/{id}/link	Link a GAM report to a template	0
POST	/reports/gam-reports/{id}/clone-to-template	Import a GAM report as a template	0
POST	/reports/templates/{id}/publish-to-gam	Publish a template to GAM	0.5
PATCH	/reports/links/{id}/sync	Sync a bridge link	0
GET	/reports/links/{id}/diff	View the diff of a bridge link	0
GET	/reports/executions	Execution history	0

MCP tools

Tool	Description	Credits
run_custom_report	Run a report with free dimensions/metrics/filters	0.5
fetch_delivery_report	Delivery report for a deployed job	0.5
fetch_inventory_report	Inventory report by ad unit	0.5
run_report_from_template	Run a saved template	0.5
export_report_csv	Export results as CSV	0.5
get_report_result	Fetch a cached result (by UUID)	0
get_report_dimensions	Dictionary of the dimensions declared per report type	0
get_report_metrics	Dictionary of the metrics declared per report type	0
get_report_date_ranges	Available date ranges	0
run_pql_query	Run a PQL query (SOAP)	0.5
generate_billing_report	Generate a GAM billing report	0.5
get_standalone_forecast	Available inventory forecast	0

Examples

Custom report via MCP

{
  "tool": "run_custom_report",
  "arguments": {
    "dimensions": ["ADVERTISER_NAME", "DATE"],
    "metrics": ["AD_SERVER_IMPRESSIONS", "AD_SERVER_CTR"],
    "date_range": "LAST_30_DAYS",
    "filters": [
      {"dimension": "COUNTRY_NAME", "operator": "EQ", "values": ["France"]}
    ]
  }
}

Report via CLI

orbiads reporting run \
  --dimensions ADVERTISER_NAME,DATE \
  --metrics AD_SERVER_IMPRESSIONS,AD_SERVER_CTR \
  --date-range LAST_30_DAYS

Notes

• Reports are run live against the Google Ad Manager API; OrbiAds keeps no persistent copy of your delivery results.
• LRO polling makes up to 20 attempts at 5-second intervals.
• Builtin templates are read-only; custom templates can be edited and deleted.
• Bridge links automatically detect configuration drift between OrbiAds and GAM.

Continue to the MCP reporting use cases

The feature page explains the product surface. The reporting pages detail the prompts, JSON payloads, dimensions and skills an agent should use.

Open the hub

GAM REST reporting hub

Understand report types, Historical counters and the REST catalogue.

Forecast JSON order/key-values

Concrete case: produce an LLM-readable forecast split by format.

Customize reporting skills

Prompts, allowed MCP functions, fields and safeguards per workflow.

Dimensions catalogue

Check the ORDER, LINE_ITEM, AD_UNIT and KEY_VALUES dimensions.

View the feature page All feature docs