Skip to main content
Glama
Sign In
OrbiAds

OrbiAds

Official
by OrbiAds
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

select_gam_network

Choose which GAM network to use for subsequent operations when multiple networks are linked. Select a network code to set it as the active network for the session.

Instructions

Set the active GAM network for the current session when the tenant has multiple linked networks.

MODE: write (session state change) AUTH: OAuth 2.0 required CREDITS: 0 (free) OUTPUT: Returns {network_code: int, display_name: string, currency: string} WHEN TO USE: Call after authentication when the tenant has more than one GAM network linked. All subsequent tool calls will use this network_code unless overridden per-call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "network_code": "<network_code>"
    },
    "name": "select_gam_network"
  }
}

Input Schema

NameRequiredDescriptionDefault
network_codeYesGAM network code to set as active.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • changedInput schema / properties / network_code / description
      Previous value: -"GAM network code to activate."New value: +"GAM network code to set as active."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

No annotations provided, so the description fully disclosures behavioral traits: it is a write operation that changes session state, requires OAuth 2.0, costs 0 credits, and returns a structured output. It also explains the side effect of setting the active network for future calls.

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?

Description is concise and well-structured: a single sentence for purpose, followed by metadata lines and usage guidelines. Every sentence provides new information without redundancy.

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 includes the output format. It covers purpose, usage, authentication, credits, and side effects, making it complete for this simple state-changing 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?

Schema coverage is 100%, so baseline is 3. The description does not add extra meaning for the parameter beyond the schema's 'GAM network code to set as active.' The usage context is helpful but does not enhance parameter semantics.

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 sets the active GAM network for the session, with a specific verb (Set) and resource (active GAM network). It distinguishes itself from siblings by focusing on network selection, which is unique among the listed tools.

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: 'Call after authentication when the tenant has more than one GAM network linked.' Also clarifies that subsequent calls use this network unless overridden, providing clear usage context and exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools