Skip to main content
Glama
OrbiAds

OrbiAds

Official

reporting

Extract delivery, custom, and forecast reports from Google Ad Manager and Google Analytics 4. Access traffic data, billing summaries, and reusable report templates.

Instructions

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

MODE: read-only (reports are read operations; report templates are saved configuration) AUTH: OAuth 2.0 required CREDITS: 0 (free) OUTPUT: Delivery/custom reports return rows of dimension+metric values. Forecasts return estimated_impressions, estimated_clicks, and confidence intervals. Report templates return template objects for reuse. 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. • For delivery analysis: check_delivery_status or fetch_delivery_report. • For custom ad-hoc reports: run_custom_report. • For forecasting: get_standalone_forecast or get_delivery_forecast_by_line_item. • For GA4 data: run_ga_report. • For reusable reports: save/run report templates. 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 forecasted impression estimate for a targeting specification without an existing line item. • 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.
Behavior2/5

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

The description declares 'MODE: read-only' but the schema includes destructive write actions like delete_report_template and delete_gam_report. While it tries to carve out template operations as 'saved configuration', the inconsistency undermines transparency. No annotations are provided to clarify.

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-organized with sections (MODE, AUTH, CREDITS, OUTPUT, WHEN TO USE, LIMITATIONS) and bullet points. It is slightly lengthy but every sentence provides value. Could be tighter by omitting redundant phrases like 'report templates are saved configuration'.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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+ sub-actions, no output schema), the description covers mode, authentication, credits, output format, usage guidance, and limitations. It lacks a generic output schema, but the output is described textually. The internal contradiction about read-only mode reduces completeness slightly.

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?

Schema description coverage is 100% due to detailed descriptions for each action enum value. The top-level description adds no further parameter-specific meaning beyond the schema, but it does provide contextual metadata (MODE, AUTH, CREDITS, OUTPUT) that aids overall understanding.

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 'Full GAM and GA4 reporting' and lists specific report types (delivery, custom, forecasting, traffic, billing). It differentiates from sibling tool reporting_skill by specifying that reporting is for direct data extraction while reporting_skill is for multi-step natural language workflows.

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 provides explicit 'WHEN TO USE' section with recommendations for reporting vs. reporting_skill, and a bulleted list mapping sub-operations to specific use cases (e.g., 'For delivery analysis: check_delivery_status'). It also mentions limitations about rejected metrics.

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