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

flin-microsoft-ads-mcp

by flin-agency

get_auth_url

Starts browser-based Microsoft Advertising sign-in on this computer, opens the authorization URL, and automatically saves the token for authenticated access.

Instructions

Start browser sign-in on this computer. Open URL; token is saved automatically.

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

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 only declare the non-destructive, non-read-only profile, so the description carries real weight and does: it discloses that a browser is opened (user interaction required) and that the token is persisted automatically with no follow-up step needed. Minor tension with openWorldHint=false since a browser sign-in reaches an external identity page, but this is a nuance rather than a contradiction.

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, both front-loaded with the action and then the side effect; no filler or redundancy.

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 parameterless, no-output-schema tool, the description covers the essential behavior: browser launch and automatic token persistence. It could add what happens if a valid token already exists or where the URL surfaces, but nothing critical is missing.

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 the baseline is 4 and there is nothing further the description could add on this axis.

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?

States a specific verb and resource: 'Start browser sign-in on this computer'. The local-browser scope and the automatic token save make the action concrete, though the sibling relationship to auth_status/clear_auth_token is left implicit.

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 by 'start browser sign-in' (call it when authentication is needed), but there is no explicit when-to-use framing, no mention of prerequisites, and no pointer to auth_status for checking existing credentials first.

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