Skip to main content
Glama
OrbiAds

OrbiAds

Official

targeting

Manage custom targeting keys, values, and ad unit configurations in Google Ad Manager to define audience segments for line items.

Instructions

Manage GAM custom targeting keys, values, and ad unit targeting configuration.

MODE: mixed (read + write) AUTH: OAuth 2.0 required CREDITS: Reads = 0. Writes = 0.5 credits. OUTPUT: Returns CustomTargetingKey objects with id, name, type (PREDEFINED/FREEFORM), and associated values. get_available_countries/languages/devices return canonical lists for geographic/device targeting. WHEN TO USE: Use targeting to manage the custom targeting vocabulary (keys and values) used in line item targeting. Use line_items to apply targeting to line items. Use inventory for ad unit structure. NOTE: get_inventory_forecast takes targeting criteria and returns estimated available impressions — useful before creating a line item to verify reach.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesSub-operation to perform: • list_ad_units: List all ad units with their sizes and status. Read-only. For full hierarchy, use inventory get_ad_unit_tree. • validate_fluid: Validate a fluid targeting expression for syntax and reference errors. Read-only. • list_custom_targeting_keys: List all custom targeting keys on the network. Read-only. • get_inventory_forecast: Get estimated available impressions for a targeting specification. Read-only. Use before creating a line item to validate reach. • create_custom_targeting_key: Create a new custom targeting key. Write. • create_custom_targeting_values: Create one or more values for an existing key. Write. • update_custom_targeting_key: Update a key's name or type. Write. • delete_custom_targeting_key: Delete a targeting key and all its values. Destructive write. • update_custom_targeting_value: Update a targeting value's name or display name. Write. • perform_custom_targeting_value_action: Activate or deactivate a targeting value. Write. • search_ad_units: Search ad units by name or path. Read-only. • update_ad_unit: Update an ad unit's name, description, or size. Write. • archive_ad_unit: Archive an ad unit. Destructive write. Run inventory find_inactive_ad_units first. • get_custom_targeting_values: Get all values for a specific targeting key. Read-only. • search_custom_targeting: Search targeting keys and values by text. Read-only. • get_available_countries: Return the canonical list of countries for geographic targeting (ISO 3166-1 alpha-2 codes). • get_available_languages: Return the canonical list of language codes for language targeting. • get_device_categories: Return the canonical list of device categories (DESKTOP, MOBILE, TABLET, CONNECTED_TV).
network_codeNoGAM network code (e.g. 12345678). Required for all network-scoped operations. Obtain via select_gam_network or list_accessible_networks.
Behavior5/5

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

With no annotations provided, the description fully bears the burden of behavioral disclosure. It clearly states MODE (mixed read+write), AUTH (OAuth 2.0 required), CREDITS (reads 0, writes 0.5), and marks destructive actions (e.g., 'Destructive write'). It also describes output objects and special cases like get_inventory_forecast.

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, CREDITS, OUTPUT, WHEN TO USE, NOTE) and each action is described concisely. While it is lengthy, every sentence provides necessary guidance. Slight redundancy in repeating 'Read-only' could be trimmed but overall earns a 4.

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 18 sub-actions and no output schema, the description is complete. It specifies return types (CustomTargetingKey objects, canonical lists), credits, authentication, and prerequisites for destructive actions. No gaps remain for an AI agent to safely invoke the tool.

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%, so baseline is 3. The description adds significant value beyond the schema by providing usage context for each action (e.g., 'Run inventory find_inactive_ad_units first' for archive_ad_unit) and clarifying scope (e.g., 'Read-only'). This justifies a 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's purpose: 'Manage GAM custom targeting keys, values, and ad unit targeting configuration.' It uses specific verbs and resources, and the 'WHEN TO USE' section distinguishes it from sibling tools like 'line_items' and 'inventory'.

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 guides when to use this tool versus alternatives: 'Use targeting to manage the custom targeting vocabulary... Use line_items to apply targeting to line items. Use inventory for ad unit structure.' Additionally, individual action descriptions note alternatives, e.g., 'For full hierarchy, use inventory get_ad_unit_tree'.

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