Skip to main content
Glama
ghl-mcp-server-v2

ghl-mcp-server-v2

by zackscriven

ghl_ad_google_current_user_get

Read-onlyIdempotent

Retrieves the authenticated Google user's info for a specified location, helping confirm which Google account is connected for ad publishing.

Instructions

Get current Google user Retrieve the authenticated Google user info for a location Endpoint: GET /ad-publishing/google/me (Version header: v3; source: v3/ad-publishing-v3.json) OAuth scopes: adPublishing.readonly

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": {
      "locationId": "<locationId>"
    },
    "name": "ghl_ad_google_current_user_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationIdYesLocation identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • removedInput schema / properties / isDraft
      Removed value: -{
      -  "description": "Is draft",
      -  "example": true,
      -  "type": "boolean"
      -}
  2. First observedv2.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the exact endpoint (GET /ad-publishing/google/me), the API version header, and the required OAuth scope adPublishing.readonly, which tells the agent what authorization the call needs. It does not describe the response shape or error modes, keeping it at 4.

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 purpose statement is front-loaded and the endpoint/scope metadata is compact. The internal line break and the '(Version header: v3; source: v3/ad-publishing-v3.json)' parenthetical are scaffolding artifacts rather than agent-facing value, which costs a point but does not obscure the core message.

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 one-parameter read with full schema coverage and complete annotations, the description supplies everything an agent needs to invoke it: resource, scoping, endpoint, and required OAuth scope. No output schema exists, but a simple 'me' lookup does not demand return-value documentation. Slightly more detail on what the returned user object contains would push it higher.

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

Parameters3/5

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

There is only one parameter and schema description coverage is 100%, with the schema documenting 'Location identifier' and an example. The description's phrase 'for a location' reinforces the semantics but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 names a specific verb and resource ('Get current Google user', 'Retrieve the authenticated Google user info for a location'), which is far more than a restatement of the name. It scopes the call to a location, which distinguishes it from the broader account-listing siblings. It stops short of naming its closest sibling (ghl_ad_google_account_get), so it is clear but not fully differentiated.

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 'the authenticated Google user' and the locationId requirement, and the OAuth scope 'adPublishing.readonly' signals a prerequisite. However, there is no explicit when-to-use/when-not guidance and no sibling tool is named as an alternative, so the agent must infer selection from the name alone.

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

Deploy Server

Other Tools