Skip to main content
Glama
OrbiAds

OrbiAds

Official

campaign

Orchestrate the lifecycle of advertising entities in Google Ad Manager, including deployment, updates, rollback, and archival.

Instructions

Orchestrate GAM campaign lifecycle — the primary write surface for creating and managing campaigns.

MODE: write-heavy (most actions modify GAM data) AUTH: OAuth 2.0 required CREDITS: deploy = 2–5 credits depending on line item count. Other write operations = 0.5–1 credit. Reads = 0. CONFIRMATION TOKEN: deploy and rollback require a confirmation_token obtained from a prior dry-run preview. This prevents accidental deployment. OUTPUT: deploy returns {campaign_id, order_id, line_item_ids[], creative_ids[], status}. rollback returns {reverted_to_version, entities_affected}. SIDE EFFECTS: deploy creates Order + LineItems + Creatives + LICAs in GAM — irreversible without rollback. rollback archives the current version and restores the previous one. WHEN TO USE: Use campaign for end-to-end campaign creation from a blueprint. Use line_items or orders for surgical updates to existing campaigns. DESTRUCTIVE: rollback and archive are non-trivial — they modify live GAM entities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesSub-operation to perform: • deploy: Deploy a complete campaign to GAM: creates Order, LineItems, Creatives, and LICAs. Requires confirmation_token. Returns campaign_id and all created entity IDs. • update: Update an existing campaign's metadata, budget, or targeting without full redeployment. Write. • ensure_template: Ensure a native ad template exists in GAM, creating it if absent. Idempotent write. • create_native_style: Create a GAM native ad style for use in native campaigns. Write. • create_line_items_batch: Create multiple line items under an existing order in one call. Write. Faster than individual line item creation. • create_licas: Create LineItem-Creative Associations (LICAs) to link creatives to line items. Write. • create_display: Create a standard display ad campaign (order + line items + creatives) from a template. Write, requires confirmation_token. • rollback: Revert a campaign to its previous deployed version. Destructive write — archives current version. Requires confirmation_token. • pause: Pause all active line items in a campaign. Write. • archive: Archive a campaign (order + line items). Destructive — removes from active serving. Requires confirmation_token.
network_codeNoGAM network code (e.g. 12345678). Required for all network-scoped operations. Obtain via select_gam_network or list_accessible_networks.
campaign_idNoOrbiAds campaign identifier (required for update/rollback/pause/archive).
confirmation_tokenNoWrite-confirmation token from a prior estimate/preview call. Required for deploy, rollback, archive.
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It comprehensively discloses behavioral traits: write-heavy mode, auth requirements, credit costs, confirmation token necessity for certain actions, detailed side effects (irreversible without rollback), and destructive nature of rollback/archive.

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 clear sections (MODE, AUTH, etc.) and front-loaded with the main purpose. However, some text repeats information already in the schema (e.g., action enum descriptions are largely redundant with schema descriptions, though the schema is part of the tool definition). Still, it is concise for the amount of detail.

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 (multiple actions, side effects, confirmation tokens), the description covers all necessary context: authentication, credits, required confirmation, output format for key actions, and destructive side effects. No output schema exists, but return values for deploy and rollback are described. It is fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the description adds significant meaning beyond the schema. The action parameter's enum values are each explained with detailed behavior, side effects, and requirements. Other parameters like network_code include sourcing instructions, campaign_id specifies the identifier type, and confirmation_token explains its origin.

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's purpose: 'Orchestrate GAM campaign lifecycle — the primary write surface for creating and managing campaigns.' It uses a specific verb (orchestrate) and resource (campaign lifecycle), and distinguishes it from siblings like line_items and orders by explicitly stating when to use each.

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?

Provides explicit usage guidance with a 'WHEN TO USE' section that tells when to use this tool (end-to-end campaign creation from a blueprint) and when to use alternatives (line_items or orders for surgical updates). Also mentions required authentication and confirmation tokens.

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