Skip to main content
Glama
OrbiAds

OrbiAds

Official
by OrbiAds
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

inventory

Manage ad unit hierarchy in Google Ad Manager: traverse tree, audit issues, batch create, generate blueprints, and sync.

Instructions

Manage GAM ad unit inventory — tree traversal, audit, batch creation, ads.txt, and blueprint sync.

MODE: mixed (read + write) AUTH: OAuth 2.0 required CREDITS: Reads = 0. Writes = 0.5–1 credit. OUTPUT: get_ad_unit_tree returns a hierarchical JSON of ad units. audit_inventory returns an analysis report. create_ad_units_batch returns a list of {requested_name, created_id, status}. SIDE EFFECTS: push_inventory_blueprint creates or updates ad units in GAM based on the stored blueprint. archive_inactive_ad_units is destructive and cannot be undone. WHEN TO USE: Use inventory for ad unit structure management. Use targeting for custom targeting keys. Use blueprint for the canonical format/position definition that drives inventory creation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesSub-operation to perform: • get_ad_unit_tree: Return the full ad unit hierarchy as a nested JSON tree. Read-only. • audit_inventory: Analyze the inventory for structural issues: orphaned ad units, duplicate sizes, missing placements. Read-only. • create_ad_units_batch: Create multiple ad units in one call from a specification list. Write. • generate_ads_json: Generate an ads.json / app-ads.json file from the current inventory. Read-only. • generate_inventory_blueprint: Generate a blueprint JSON from existing GAM inventory (reverse-engineering). Read-only. • push_inventory_blueprint: Push the stored blueprint to GAM, creating or updating ad units. Write, 1 credit. • get_ad_units_by_ids: Retrieve multiple ad units by ID in one call. Read-only. • find_inactive_ad_units: Find ad units with no recent impressions. Read-only. • archive_inactive_ad_units: Archive ad units flagged as inactive. Destructive write. Run find_inactive_ad_units first. • list_ad_unit_sizes: List all sizes used across ad units on the network. Read-only.
network_codeNoGAM network code (e.g. 12345678). Required for all network-scoped operations. Obtain via select_gam_network or list_accessible_networks.

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

Despite no annotations, description fully discloses mode (mixed read+write), auth requirements (OAuth), credit costs, output formats for key actions, and side effects (e.g., destructive nature of archive_inactive_ad_units).

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?

Description is compact (~150 words) and well-structured with sections (MODE, AUTH, CREDITS, OUTPUT, SIDE EFFECTS, WHEN TO USE). Every sentence serves a purpose.

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 complexity of 10 sub-operations and no output schema, the description covers all necessary context: mode, auth, credits, side effects, usage guidance, and output format for key actions.

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 has 100% coverage with detailed enum descriptions for each action and network_code parameter. The description text does not add new information beyond summarizing the schema, meeting the baseline for high schema coverage.

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?

Description clearly states the tool manages GAM ad unit inventory with specific sub-operations like tree traversal, audit, batch creation. It also distinguishes from sibling tools like targeting and blueprint.

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?

Explicit WHEN TO USE section directs agents to use inventory for ad unit structure, targeting for custom targeting keys, and blueprint for canonical format. Additionally, within action descriptions, it provides chaining instructions (e.g., run find_inactive_ad_units first before archive).

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