Skip to main content
Glama
OrbiAds

OrbiAds

Official

blueprint

Define and manage your Google Ad Manager inventory blueprint including ad formats, positions, key-values, and brand settings to standardize campaign generation.

Instructions

Manage the tenant inventory blueprint — the canonical definition of ad formats, positions, key-values, and brand settings used to generate GAM campaigns.

MODE: mixed (read + write) AUTH: OAuth 2.0 required CREDITS: Reads = 0. Writes (save_blueprint, save_preferences, add/remove operations) = 0 credits but modify persistent tenant configuration. OUTPUT: get_active_blueprint returns the full blueprint JSON with formats, positions, keyValues, brand. list_templates returns available campaign templates. SIDE EFFECTS: Changes to the blueprint affect all future campaign deployments that reference it. Removing a format or position does not remove existing GAM line items. WHEN TO USE: Use blueprint to define or update the standard inventory structure before running campaign. Use formats tool for the Custom Format Registry (creative format recipes, not inventory positions).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesSub-operation to perform: • get_active_preferences: Read the current tenant preferences (naming conventions, default targeting, delivery settings). • get_active_blueprint: Read the full active inventory blueprint JSON. • save_blueprint: Replace the full blueprint with a new version. Write. Validate with a dry-run before saving to production. • save_preferences: Update tenant preferences. Write. • add_format: Add a creative format to the blueprint. Write. Requires format_code and size parameters. • remove_format: Remove a creative format from the blueprint. Write. Does not remove existing GAM creatives. • add_position: Add an inventory position (ad unit + targeting combination) to the blueprint. Write. • remove_position: Remove an inventory position from the blueprint. Write. Does not archive existing ad units. • add_key_value: Add a custom targeting key-value definition to the blueprint. Write. • remove_key_value: Remove a key-value definition from the blueprint. Write. • update_brand: Update brand metadata (name, logo, primary color) attached to the blueprint. Write. • update_platforms: Update the list of target platforms (desktop, mobile_web, app_ios, app_android) in the blueprint. Write. • list_templates: List all available campaign templates (display, native, video presets). Read-only.
network_codeNoGAM network code (e.g. 12345678). Required for all network-scoped operations. Obtain via select_gam_network or list_accessible_networks.
Behavior4/5

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

With no annotations, the description fully covers mode (mixed read/write), auth requirements, credits (0 for writes but modifies config), and side effects (changes affect future campaigns). Could be slightly more explicit about write reversibility, but overall strong.

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 sections like MODE, AUTH, OUTPUT, SIDE EFFECTS, and WHEN TO USE. While slightly lengthy, every sentence adds value, and the main purpose 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 two parameters and 100% schema coverage, the description provides complete context for all actions, including output descriptions for key sub-operations. No output schema is needed as the tool returns blueprint JSON.

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% with detailed enum descriptions. The description adds extra context beyond the schema (e.g., 'Validate with a dry-run before saving to production'), raising the baseline from 3 to 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 manages the tenant inventory blueprint, specifying it covers ad formats, positions, key-values, and brand settings. It also distinguishes from the 'formats' sibling tool.

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 vs. alternatives (formats tool), providing clear guidance for the 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