Skip to main content
Glama
flin-google-ads-mcp

flin-google-ads-mcp

by flin-agency

get_auth_url

Starts automatic local OAuth capture for Google Ads and returns an authorization URL to open, so authentication completes without copying codes.

Instructions

Start automatic local OAuth capture. Open the returned URL; no code copying is needed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_auth_url"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.13

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and the description adds that capture is local and automatic with no code copying, which clarifies the side-effect profile. It does not mention that a local listener/browser interaction is triggered or how completion is detected (e.g., polling a status tool), so behavioral context is partial.

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?

Two short sentences, front-loaded with the action and then the immediate next step; no filler or redundant restatement of the name.

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

Completeness4/5

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

With zero parameters and an output schema covering the returned URL, the description supplies what an agent needs to act. It stops just short of explaining the completion handoff (how the agent knows auth succeeded), which would fully close the loop.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate beyond confirming the call is argument-free.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific action (start automatic local OAuth capture) and the resource (OAuth), and the clause 'no code copying is needed' implicitly distinguishes it from the code-based sibling flow (save_refresh_token_from_code). It doesn't name that sibling outright, so differentiation is inferential rather than explicit.

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

Usage Guidelines3/5

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

Gives a procedural hint ('Open the returned URL') and implicitly contrasts with a code-copying path, but never states when this flow should be chosen over auth_status or save_refresh_token_from_code, nor what to do after opening the URL.

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