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

flin-microsoft-ads-mcp

by flin-agency

clear_auth_token

Destructive

Deletes the locally stored Microsoft Advertising refresh token and cancels any pending browser sign-in, letting you reset authentication without revoking Microsoft consent.

Instructions

Delete the local refresh token and cancel pending sign-in. Does not revoke Microsoft consent.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description earns credit for going beyond that by identifying what is destroyed (the local refresh token), that pending sign-in is canceled, and the important boundary that Microsoft-side consent survives. It does not say whether the call errors or no-ops when no token is present, which is the remaining behavioral gap.

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, zero filler, with the destructive effect front-loaded and the scope caveat second. Nothing here could be removed without losing information.

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?

For a zero-parameter mutation with no output schema, the description covers the action, its local scope, and its limits, which is most of what an agent needs. Only the idempotency / no-token-present case is left unaddressed.

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 no parameter meaning to convey; baseline 4 applies. The description does not waste words inventing parameter detail that does not exist.

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?

Uses a specific verb ('Delete') and a precisely scoped resource ('the local refresh token'), and adds 'cancel pending sign-in' so the effect is unambiguous. It stops short of naming a sibling to contrast with (e.g. auth_status or get_auth_url), but the local-only scope makes it distinguishable from those tools on their names alone.

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 stated: the agent can infer 'sign out / abort a sign-in' from the wording, and 'Does not revoke Microsoft consent' hints at a when-not condition. There is no explicit instruction about when to prefer this over re-authenticating or checking auth_status first.

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