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

flin-google-ads-mcp

by flin-agency

connection_status

Read-only

Reports Google Ads setup status without network access; set check_live to true to explicitly test account access without returning customer data.

Instructions

Report setup without network access by default. check_live=True explicitly tests Google Ads access; no customer data is returned.

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": "connection_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
check_liveNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.13

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the readOnly/destructive annotations, it discloses that the default run makes no network calls, that check_live=True performs a live Google Ads access test, and that no customer data is returned - real behavioral context an agent couldn't get from annotations alone.

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?

Two short sentences, default behavior front-loaded, then the opt-in flag. No filler, though the opening clause reads slightly clipped and could name the resource more explicitly.

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?

An output schema exists so return structure needn't be described, and the description covers the one decision (offline vs. live) plus the no-customer-data guarantee. Adequate for a single-parameter diagnostic tool.

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 0%, so the description must explain the lone parameter, and it does: check_live=True means explicitly test Google Ads access, with false as the no-network default. Only the exact nature of the live test (auth check vs. API call) is left unstated.

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

Purpose3/5

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

"Report setup" describes a status/diagnostic tool, and the offline-by-default behavior hints at its scope, but the verb-resource pairing is loose ('setup' rather than connection or credentials) and nothing distinguishes it from siblings like health_check or auth_status.

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?

It gives a clear rule for the parameter switch (check_live=True for a live Google Ads test, default stays offline), which is implicit when-to-use guidance, but it never says when to choose this tool over auth_status or health_check.

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