Skip to main content
Glama
flin-gmp-mcp

flin-gmp-mcp

by flin-agency

authenticate

Sign in to Google Marketing Platform via a local browser, store credentials privately per account alias, and replace a saved sign-in only after successful new authorization.

Instructions

Sign in via the local browser and store credentials privately; never returns tokens.

Uses a Desktop OAuth client and a loopback callback (180-second timeout). Choose a lower-case account alias such as work for a separate login. force=true replaces the selected account's saved sign-in only after a successful new authorization. Requests permissions for GOOGLE_GMP_SERVICES; some Google scopes also allow writes, but this server only exposes reads and DV360 report creation/runs. Requires a browser on the server host.

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

Input Schema

NameRequiredDescriptionDefault
forceNo
accountNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

The annotations only declare non-read-only, open-world, non-idempotent, and non-destructive. The description adds material context beyond that: a Desktop OAuth client, a loopback callback with a 180-second timeout, a requirement for a browser on the server host, and the fact that credentials are stored but tokens are not returned. The `force` replacement is also qualified as occurring only after a successful new authorization, which softens the destructive reading.

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?

The core action is front-loaded in the first sentence, and the remaining sentences each carry operational detail. The aside about GOOGLE_GMP_SERVICES scopes permitting writes while the server only exposes reads and DV360 report creation is somewhat tangential but does set correct expectations.

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?

Given a two-parameter authentication tool with an output schema, the description covers the prerequisites (browser on host, loopback callback), the timeout, the credential storage behavior, and the force/account semantics. An agent has what it needs to call this correctly without inspecting the schema.

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 coverage is 0%, so the description must carry both parameters, and it largely does: `force` is explained as replacing the selected account's saved sign-in only after success, and `account` is explained as a lower-case alias such as `work` for an isolated login. It stops short of stating defaults or what a null/missing account means, so it is slightly incomplete rather than fully compensating.

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?

The description states a specific action and mechanism: sign in via a local browser, store credentials privately, and never return tokens. That is precise enough to separate this from every sibling, all of which are data-read or status tools.

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?

Usage is implied rather than directed: the reader infers this is the prerequisite for the other tools, and the description does say to use `force` to re-authorize and an account alias for a separate login. What is missing is explicit routing, e.g. checking connection_status first or what happens if already signed in.

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