Skip to main content
Glama
flin-google-keyword-planner-mcp

flin-google-keyword-planner-mcp

by flin-agency

connection_status

Read-onlyIdempotent

Reports local server setup and running version without network access or login, so you can verify configuration before using Google Ads tools; no OAuth or API quota used.

Instructions

Report local setup and the running server version, without network or login.

A local refresh token does not prove valid Google authorization. This tool never starts OAuth, refreshes a token, or consumes Google Ads API quota.

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

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the bar is lower; the description still adds real value by enumerating side effects it does not perform — no OAuth start, no token refresh, no Google Ads API quota consumption. That negative-space disclosure is exactly what an agent needs before calling an environment-inspection tool.

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 paragraphs, front-loaded with the primary action, then the caveat. The token remark is slightly out of the blue with no antecedent, but it earns its place as a misuse guard rather than filler.

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 values need not be spelled out, and with zero parameters the surface area is small. The description covers what the tool does, what it explicitly does not do, and what environment it requires — sufficient for correct invocation.

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 there is nothing for the description to disambiguate and the baseline applies. The schema adds no meaning that the description needs to compensate for.

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?

The description states a concrete action and scope: reporting local setup plus the running server version. "Local setup" is slightly fuzzy as a resource label, but the second paragraph pins the boundary by telling the agent this is not a Google authorization check, which separates it from the OAuth siblings.

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

Usage Guidelines4/5

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

It sets the context clearly (offline, no login, no API quota) and warns against a specific misuse — treating a local refresh token as proof of valid Google authorization. It never names the alternative sibling to call when you do need authorization status, so guidance is clear but not fully routed.

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