Skip to main content
Glama
Sign In
OrbiAds

OrbiAds

Official
by OrbiAds
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

poll_auth_status

Check the status of a Google Ad Manager OAuth authorization request by polling until it returns authorized or failed.

Instructions

Poll the OAuth authorization status after initiating a GAM auth flow.

MODE: read-only AUTH: OrbiAds session required CREDITS: 0 (free) OUTPUT: Returns {status: 'pending'|'authorized'|'failed', error?: string} WHEN TO USE: Call repeatedly (every 2–5 seconds) after initiate_gam_auth until status = 'authorized' or 'failed'.

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": {
      "session_id": "<session_id>"
    },
    "name": "poll_auth_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesAuth session ID returned by initiate_gam_auth.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description fully compensates by including MODE (read-only), AUTH requirements, CREDITS, and OUTPUT format. It clearly sets expectations about side effects and behavior.

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 labeled sections (MODE, AUTH, CREDITS, OUTPUT, WHEN TO USE). Every sentence serves a purpose, no 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?

For a single-parameter polling tool with no output schema, the description covers purpose, usage context, behavior, auth, and expected output format completely.

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% and the description adds no additional detail beyond the schema's parameter description. The context of use is implied, but no new semantic information is provided for the parameter itself.

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?

Clearly states 'Poll the OAuth authorization status after initiating a GAM auth flow', specifying the verb (poll), resource (authorization status), and context (after initiate_gam_auth), distinguishing it from sibling tools like initiate_gam_auth.

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 provides 'WHEN TO USE' with specific instructions: 'Call repeatedly (every 2–5 seconds) after initiate_gam_auth until status = \'authorized\' or \'failed\''. This gives clear context and timing guidance.

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