Skip to main content
Glama
OrbiAds

OrbiAds

Official

reporting

Run GAM and GA4 reports: track delivery, drill down with custom dimensions and metrics, forecast availability, and manage saved templates. Get data-driven insights for ad operations.

Instructions

Full GAM and GA4 reporting — delivery reports, custom reports, forecasting, traffic data, billing, and report management.

MODE: mixed (read + write) READ: all report-run, forecast, list, get, and discovery actions (majority of actions) WRITE: save_report_template (creates), update_report_template (mutates), duplicate_report_template (creates), delete_report_template (destructive), create_gam_report (creates in GAM), update_gam_report (mutates in GAM), delete_gam_report (destructive soft-delete — PATCH visibility=HIDDEN) AUTH: OAuth 2.0 required CREDITS: 0 (all actions free) OUTPUT: Delivery/custom reports return rows of dimension+metric values. Forecasts return estimated_impressions, estimated_clicks, and confidence intervals. Template/GAM report actions return the object after mutation. SIDE EFFECTS: • delete_report_template permanently removes the template from the tenant — irreversible. • delete_gam_report uses soft-delete (PATCH visibility=HIDDEN on the GAM REST API) — the report is hidden from the UI but not purged; there is no DELETE endpoint on GAM reports. • save_report_template and create_gam_report persist new entities that count against quotas. WHEN TO USE: Use reporting for all data extraction and analysis. Use reporting_skill for high-level multi-step reporting workflows described in natural language. • Delivery analysis: check_delivery_status or fetch_delivery_report. • Custom ad-hoc reports: run_custom_report. • Forecasting: get_standalone_forecast or get_delivery_forecast_by_line_item. For pre-flight feasibility, pass sizes/creativeSizes, geo/geoTargeting, priority, frequencyCaps, lineItemType and cpmMicroAmount so the estimate is constrained like the planned Line Item. • GA4 data: run_ga_report. • Reusable reports: save_report_template / run_report_from_template. LIMITATIONS: Some SOAP-era metrics (TOTAL_*, AD_SERVER_ALL_REVENUE) and dimensions (MONTH_AND_YEAR, CREATIVE_SIZE) are rejected by the REST API. Use get_report_dimensions/get_report_metrics to discover valid options.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesSub-operation to perform: • check_delivery_status: Check delivery status (actual vs booked) for an order or line item. Returns pacing indicator. • fetch_delivery_report: Fetch a delivery report for a date range. Returns impressions, clicks, CTR by line item. • run_custom_report: Run an ad-hoc report with specified dimensions and metrics. Returns result rows. • fetch_inventory_report: Fetch an inventory forecast report for ad units. Returns available impressions. • get_report_result: Retrieve the result of a previously run report by report_id. • export_report_csv: Export a report result as a CSV download URL. • get_report_dimensions: List valid dimension names for custom reports. Use to discover available breakdown options. • get_report_metrics: List valid metric names for custom reports. Use to discover available measurements. • get_report_date_ranges: List valid relative date range strings (LAST_7_DAYS, LAST_MONTH, etc.). • get_standalone_forecast: Get a constrained forecast for a prospective line item. Accepts adUnitIds, startDate, endDate, sizes/creativeSizes, geo/geoTargeting, priority, frequencyCaps, lineItemType and cpmMicroAmount. • get_delivery_forecast_by_line_item: Get a delivery forecast for one or more existing line items. • get_prospective_delivery_forecast: Get a prospective forecast for a hypothetical line item configuration. • get_traffic_data: Get historical traffic data (impressions available) for targeting criteria. • list_report_templates: List saved report templates. Read-only. • save_report_template: Save a report configuration as a reusable template. Write. • delete_report_template: Delete a report template. Destructive write. • duplicate_report_template: Duplicate a report template. Write. • update_report_template: Update a saved report template. Write. • run_report_from_template: Run a report using a saved template. Returns report_id for async result retrieval. • list_gam_reports: List reports saved in the GAM UI. Read-only. • get_gam_report: Get a specific GAM report by ID. Read-only. • create_gam_report: Create a new report in GAM. Write. • update_gam_report: Update a GAM report configuration. Write. • delete_gam_report: Delete a GAM report. Destructive write — uses soft-delete (PATCH visibility=HIDDEN). • run_gam_report: Run a GAM report and return result rows. • run_ga_report: Run a GA4 report for connected Google Analytics data. • get_ga_dimensions: List valid GA4 dimension names. • get_ga_metrics: List valid GA4 metric names. • check_underdelivery_alerts: Check for active underdelivery alerts across all line items. Returns affected line items with severity. • check_budget_alerts: Check for budget pacing alerts. Returns line items at risk of overspending. • generate_billing_report: Generate a billing summary report for a date range. Returns revenue by advertiser and line item.
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?

Despite no annotations, the description fully discloses behavioral traits: it states the mode (mixed read+write) and categorizes actions, details side effects (e.g., irreversible delete for templates, soft-delete for GAM reports, quota implications), lists authentication and credit requirements, describes output formats, and notes limitations (rejected SOAP-era metrics/dimensions). No contradictions with annotations (none provided).

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 well-structured with clear sections (intro, MODE, AUTH, CREDITS, OUTPUT, SIDE EFFECTS, WHEN TO USE, LIMITATIONS). It is front-loaded with the overall purpose, and every sentence adds necessary information without redundancy.

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 (30+ actions), the description comprehensively covers all aspects: purpose, read/write mode, authentication, credits, output formats, side effects, usage guidelines, and limitations. No output schema exists, but the OUTPUT section adequately explains return types. The description is complete for an AI agent to correctly select and invoke the tool.

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 value beyond the schema by providing strategic guidance on parameter usage for forecasting (e.g., 'For pre-flight feasibility, pass sizes/creativeSizes...'). This extra context justifies a score of 4.

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 covers 'Full GAM and GA4 reporting' including delivery reports, custom reports, forecasting, traffic data, billing, and report management. It distinguishes from sibling 'reporting_skill' by specifying when to use each tool, making the purpose and scope unmistakable.

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 to use this tool for all data extraction and analysis, and 'reporting_skill' for high-level multi-step workflows. It also provides specific use cases for delivery analysis, custom reports, forecasting, etc., including detailed advice for forecasting parameters.

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