Skip to main content
Glama
OrbiAds

OrbiAds

Official

gam_admin

Configure and govern your GAM network by managing teams, users, sites, mobile apps, custom fields, labels, and publisher signals.

Instructions

GAM admin orchestration — 48 operations across 7 administrative areas: Teams, Sites, Mobile Apps, Custom Fields, Labels, Publisher Provided Signals, and Users.

MODE: mixed (read + write) AUTH: OAuth 2.0 required — user must have Network Admin role for write operations CREDITS: Reads = 0. Writes = 0.5 credits. OUTPUT: Returns administrative entity objects specific to the sub-area (Team, Site, MobileApp, CustomField, Label, PublisherProvidedSignalsConfig, User objects). SIDE EFFECTS: User management operations (deactivate, remove) affect access control. Label and custom field changes propagate to existing entities. Team changes affect inventory access rights. WHEN TO USE: Use gam_admin for network configuration and governance tasks (team structure, user management, custom metadata). Use targeting for custom targeting key-values used in ad serving.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesSub-operation to perform: • list_teams: List all teams on the network. Read-only. • get_team: Get a team by ID. Read-only. • create_team: Create a new team. Write. • update_team: Update a team's name or description. Write. • delete_team: Delete a team. Destructive write — removes team membership associations. • add_team_members: Add users to a team. Write. • remove_team_members: Remove users from a team. Write. • list_sites: List all sites on the network. Read-only. • get_site: Get a site by ID. Read-only. • create_site: Create a new site. Write. • update_site: Update a site. Write. • delete_site: Delete a site. Destructive write. • list_mobile_apps: List mobile apps registered on the network. Read-only. • get_mobile_app: Get a mobile app by ID. Read-only. • create_mobile_app: Register a new mobile app. Write. • update_mobile_app: Update a mobile app's details. Write. • list_custom_fields: List all custom fields defined on the network. Read-only. • get_custom_field: Get a custom field by ID. Read-only. • create_custom_field: Create a custom field for orders, line items, or creatives. Write. • update_custom_field: Update a custom field's name or options. Write. • deactivate_custom_field: Deactivate a custom field. Soft delete — preserves existing values. • list_custom_field_options: List options for a custom field of type SELECT. Read-only. • create_custom_field_option: Add a new option to a SELECT custom field. Write. • update_custom_field_option: Update a custom field option. Write. • deactivate_custom_field_option: Deactivate a custom field option. Write. • list_labels: List all labels. Read-only. • get_label: Get a label by ID. Read-only. • create_label: Create a new label. Write. • update_label: Update a label. Write. • deactivate_label: Deactivate a label. Write. • list_pps_configs: List Publisher Provided Signals configurations. Read-only. • get_pps_config: Get a PPS config by ID. Read-only. • create_pps_config: Create a PPS configuration. Write. • update_pps_config: Update a PPS configuration. Write. • delete_pps_config: Delete a PPS configuration. Destructive write. • list_users: List all users on the network. Read-only. • get_user: Get a user by ID. Read-only. • get_current_user: Get the currently authenticated user's profile. Read-only. • create_user: Create a new user account. Write. • update_user: Update a user's role or email. Write. • deactivate_user: Deactivate a user account. Write — revokes network access. • perform_user_action: Perform a lifecycle action on a user (ACTIVATE, DEACTIVATE). Write. • list_roles: List all roles available on the network. Read-only. • list_team_memberships: List team memberships for a user. Read-only. • get_user_record: Get a user's full record including role and team assignments. Read-only. • get_salesperson_record: Get salesperson metadata for a user. Read-only. • get_trafficker_record: Get trafficker metadata for a user. Read-only. • audit_user_access: Audit user access rights: roles, teams, and accessible inventory. 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?

No annotations provided, so description carries full burden. It covers side effects (user deactivation/removal affects access control, label changes propagate), auth needs, credit costs (reads=0, writes=0.5), and output types per sub-area. Does not mention rate limits or error conditions, but given complexity, it's thorough.

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?

Well-structured with headings (MODE, AUTH, CREDITS, OUTPUT, SIDE EFFECTS, WHEN TO USE). Front-loaded with summary. Could be slightly more concise, but organization aids readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers many aspects (side effects, auth, credits, when to use). However, fails to mention that sub-operations may require additional parameters beyond action and network_code (schema has additionalProperties: true). Also lacks return value format details. Adequate but incomplete.

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% with detailed enum descriptions for action and network_code. The description adds overall context (auth, credits) but does not significantly enhance individual parameter meaning beyond the schema. Baseline 3 is appropriate.

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?

Description clearly states it's a GAM admin orchestration tool with 48 operations across 7 administrative areas. It provides a specific verb+resource summary and distinguishes from sibling 'targeting' tool in the WHEN TO USE section.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

WHEN TO USE section explicitly recommends using gam_admin for network configuration and governance tasks, and suggests targeting for custom targeting key-values. Auth requirements (OAuth 2.0, Network Admin role for writes) are stated. Lacks explicit exclusion of other sibling tools but provides clear context.

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