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

flin-google-ads-mcp

by flin-agency

save_refresh_token_from_code

Destructive

Stores a Google Ads refresh token from an authorization code as a manual fallback when automatic token capture fails.

Instructions

Legacy manual fallback; get_auth_url normally captures and stores the token automatically.

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": {
      "code": "<code>"
    },
    "name": "save_refresh_token_from_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.13

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the write nature is covered structurally. The description adds the useful context that this is a legacy path superseded by get_auth_url, but it never explains what the destructive flag means here (e.g. overwriting an existing refresh token) or whether any prior credentials are replaced.

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?

One sentence, front-loaded with the key qualifier ("Legacy manual fallback") and with no filler. It is arguably over-terse for a destructive mutation, but nothing in it is wasted.

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

Completeness3/5

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

The tool is simple (one param) and has an output schema, so full return-value documentation is unnecessary. However, for a destructive write with an entirely undocumented parameter, the definition leaves out what the code is and what state it changes, which is the information an agent most needs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the single parameter "code" is left completely undefined in both schema and description. The agent must guess that this is an OAuth authorization code rather than, say, a device code or customer ID, and gets no hint about where to obtain it.

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?

"Legacy manual fallback" is a role label rather than a verb+resource, so the actual action (exchanging an authorization code for a stored refresh token) is only inferable from the tool name. It does, however, contrast itself with the sibling get_auth_url, which helps an agent place it in the auth flow.

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?

The definition clearly implies the when: use this only when the normal path fails, because get_auth_url "normally captures and stores the token automatically." That is a usable routing rule, though it never states the fallback trigger explicitly or warns against using it when the automatic path already succeeded.

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