Skip to main content
Glama
OrbiAds

OrbiAds

Official

network

Retrieve current GAM network details, switch active network, list accessible networks, and update network settings like display name or currency.

Instructions

GAM network management — get info, switch active network, list accessible networks, update settings.

MODE: mixed (read + write) AUTH: OAuth 2.0 required CREDITS: Reads = 0. update_network = 0.5 credits. OUTPUT: get_network_info returns {networkCode, displayName, currencyCode, timeZone, effectiveRootAdUnit}. list_accessible_networks returns all networks the authenticated user can access. WHEN TO USE: Use network to discover and switch between multiple GAM networks. Call list_accessible_networks after authentication to find available networks, then switch_network to set the active one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesSub-operation to perform: • get_network_info: Return metadata about the current active GAM network. • switch_network: Set a different network as the active one for subsequent operations. Requires network_code of the target network. • list_accessible_networks: List all GAM networks accessible to the authenticated Google account. • update_network: Update network-level settings (display name, currency). Write, requires Network Admin role.
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, but the description compensates by stating MODE (mixed), AUTH (OAuth 2.0), and CREDITS per operation. It also details return values for get_network_info and list_accessible_networks. However, it does not explicitly mention that switching or updating may have side effects, though those are implied.

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). It is slightly verbose but each sentence adds value. Front-loaded with summary.

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 no output schema, the description thoroughly explains return values and behavior. The tool has only 2 parameters with simple enum, and the description covers all necessary context for an agent to use it correctly.

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 description coverage is 100%. The description adds value beyond schema by providing context for network_code ('Obtain via select_gam_network or list_accessible_networks') and detailing each action's purpose and requirements.

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 that the tool is for 'GAM network management' and lists specific sub-operations: get info, switch, list, update. This distinguishes it from sibling tools that handle different entities like audiences, orders, etc.

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' paragraph that explicitly explains usage: after authentication, call list_accessible_networks to find networks, then switch_network to set active. It also provides context for each sub-operation.

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