Skip to main content
Glama
OrbiAds

OrbiAds

Official

deals

Create, update, and manage programmatic deals including PMP, PG/PD proposals, ADCP deal flows, and auction packages in Google Ad Manager.

Instructions

Author and manage programmatic deals — PMP, PG/PD proposals, ADCP deal flows, and auction packages.

MODE: mixed (read + write) AUTH: OAuth 2.0 required CREDITS: Reads = 0. Write operations = 0.5–2 credits. ADCP create = 2 credits. OUTPUT: Returns Deal or Proposal objects with id, status, buyerId, floorPrice, targeting, and negotiation state. SIDE EFFECTS: Proposals go through a negotiation workflow — state transitions (reserve, request_buyer_acceptance) trigger buyer notifications. terminate_proposal_negotiations is irreversible. WHEN TO USE: Use deals for programmatic direct (PG/PD), private marketplace (PMP), and ADCP deal creation. For standard direct-sold campaigns, use campaign tool instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesSub-operation to perform: • list_deals: List all programmatic deals on the network. Read-only. • get_deal: Get a specific deal by ID. Read-only. • create_deal: Create a new programmatic deal. Write. • update_deal: Update a deal's floor price or targeting. Write. • list_auctions: List auction packages. Read-only. • get_auction: Get a specific auction package. Read-only. • create_auction: Create an auction package. Write. • update_auction: Update an auction package. Write. • list_buyers: List all programmatic buyers on the network. Read-only. • get_buyer: Get a specific buyer by ID. Read-only. • get_proposal: Get a proposal by ID including its negotiation history. Read-only. • create_proposal: Create a new PG/PD proposal. Write. • update_proposal: Update a proposal's terms, targeting, or pricing. Write. • archive_proposal: Archive a proposal. Destructive write. • request_buyer_acceptance: Send a proposal to the buyer for acceptance. Write — triggers buyer notification. • reserve_proposal: Reserve inventory for a proposal (locks availability). Write. • edit_proposal_for_negotiation: Reopen an accepted proposal for renegotiation. Write. • terminate_proposal_negotiations: Permanently terminate negotiations. Irreversible destructive write. • get_marketplace_comments: Retrieve buyer/seller comments on a proposal. Read-only. • list_proposal_line_items: List line items within a proposal. Read-only. • create_proposal_line_items: Create line items within a proposal. Write. • update_proposal_line_items: Update proposal line items' targeting or pricing. Write. • archive_proposal_line_items: Archive proposal line items. Destructive write. • create_makegoods: Create makegood line items to compensate for underdelivered campaigns. Write. • estimate_deal_cost: Preview the credit cost of a deal operation. Read-only. • adcp_validate: Validate an ADCP deal configuration before creation. Read-only. • adcp_preview: Preview an ADCP deal's reach and estimated delivery. Read-only. • adcp_create: Create an ADCP deal. Write, 2 credits, 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.
Behavior4/5

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

Despite no annotations, the description provides mode (mixed read+write), auth requirements (OAuth), credit costs per operation, side effects (state transitions, buyer notifications, irreversibility of termination). It lacks rate limit info but covers key behavioral traits well.

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 labels (MODE, AUTH, CREDITS, etc.) and bullet-style action list. It is fairly long but most sentences add unique value. Could be more concise, but organization aids readability.

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?

For a complex tool with 2 parameters and no output schema, the description covers output types, side effects, and credit costs. It lacks explicit mention of error handling or pagination but is otherwise complete for agent decision-making.

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 coverage is 100%, so the baseline is 3. The description adds overall context like side effects and usage but does not provide additional detail on parameters beyond what the schema already includes. For high coverage, description adds marginal value.

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 authors and manages programmatic deals (PMP, PG/PD, ADCP, auction packages). It distinguishes from siblings by specifying to use the campaign tool for standard direct-sold campaigns. The summary verb 'Author and manage' plus the list of deal types provides precise scope.

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?

Explicitly states when to use (programmatic direct, PMP, ADCP) and when not to (direct-sold campaigns, pointing to campaign tool). Also provides credit costs and side effects like negotiation workflows, giving clear context for agent decisions.

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