Skip to main content
Glama
OrbiAds

OrbiAds

Official

line_items

Manage individual line items in Google Ad Manager with CRUD operations, targeting updates, duplication, verification, and creation of programmatic types like Ad Exchange, Open Bidding, and Preferred Deals.

Instructions

Non-lifecycle Line Item operations — get, list, update, duplicate, verify, and create programmatic types.

MODE: mixed (read + write) AUTH: OAuth 2.0 required CREDITS: Reads = 0. Writes = 0.5 credits. OUTPUT: Returns LineItem objects with id, name, type, startDateTime, endDateTime, costType, unitsBought, targeting, and deliveryIndicator. WHEN TO USE: Use line_items for individual line item CRUD and programmatic line item creation. Use campaign for full campaign orchestration. Use line_item_lifecycle for status transitions (activate/pause/archive). NOT the same as line_item_lifecycle: line_items handles data updates; line_item_lifecycle handles status transitions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesSub-operation to perform: • get: Get a single line item by ID. Read-only. • list_by_order: List all line items under an order. Read-only. Requires order_id. • update: Update a line item's name, targeting, dates, or budget. Write. • update_targeting: Update only the targeting of a line item. Write. More efficient than full update for targeting-only changes. • duplicate: Duplicate a line item to create a copy. Write. • verify: Verify that a line item configuration is valid before activation. Read-only. • approve: Approve a line item for delivery. Write. • archive: Archive a line item. Destructive write. • create_batch: Create multiple standard line items under an order. Write. • activate_batch: Activate multiple line items in one call. Write. • pause_batch: Pause multiple line items in one call. Write. • create_adexchange: Create an Ad Exchange line item. Write. Requires adExchangeEnvironment and targeting. • create_open_bidding: Create an Open Bidding line item. Write. Requires yieldGroupIds. • create_preferred_deal: Create a Preferred Deal line item. Write. Requires fixedCpm and buyerId. • list_private_deals: List Private Marketplace deals associated with line items. Read-only.
network_codeNoGAM network code (e.g. 12345678). Required for all network-scoped operations. Obtain via select_gam_network or list_accessible_networks.
line_item_idNoGAM Line Item ID (required for single-entity operations).
order_idNoGAM Order ID (required for list_by_order and create_batch).
Behavior4/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It conveys that the tool is mixed read+write, requires OAuth 2.0, consumes credits (reads = 0, writes = 0.5), and lists output fields. However, it could be more explicit about destructive operations beyond 'archive' and the consequences of batch operations.

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?

The description is well-structured with clear sections (summary, mode, auth, credits, output, when to use). It is concise, using bullet points and short paragraphs, with every sentence adding value. No redundancy or unnecessary information.

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?

Despite having 4 parameters and no output schema, the description provides comprehensive context: authentication, credit costs, output field list, explicit usage guidance against siblings, and a detailed action enum summary. This fully compensates for the missing output schema and ensures the agent can correctly invoke the tool.

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?

The input schema has 100% description coverage, meaning all parameters already have clear descriptions. The tool description adds a summary of the action enum but does not provide additional semantic value beyond what the schema offers. Baseline is 3, which is appropriate here.

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 explicitly states 'Non-lifecycle Line Item operations — get, list, update, duplicate, verify, and create programmatic types,' clearly defining the tool's purpose as CRUD and programmatic creation for line items. It also distinguishes from siblings like 'line_item_lifecycle' and 'campaign', ensuring no ambiguity.

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 includes a 'WHEN TO USE' section that explicitly contrasts this tool with 'campaign' and 'line_item_lifecycle', stating that line_items handles individual CRUD and programmatic creation, while others handle orchestration or status transitions. This provides clear guidance on when to use each tool.

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