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

ghl-mcp-server-v2

by zackscriven

ghl_ad_li_current_user_get

Read-onlyIdempotent

Retrieve the authenticated LinkedIn user for a specific location to verify account identity and ad publishing access. Requires a location ID and read-only ad publishing scope.

Instructions

Get current LinkedIn user Retrieve the authenticated LinkedIn user info for a location Endpoint: GET /ad-publishing/linkedin/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_li_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.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior, so the bar is lower. The description adds genuinely useful context beyond annotations: the required OAuth scope (adPublishing.readonly), the endpoint path, and the API version header. It does not describe what user fields are returned, but it meaningfully adds auth and endpoint context.

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 description is front-loaded with the action and resource, then layers in endpoint, version, and OAuth scope. The metadata lines are dense but each serves a purpose for an agent that needs to understand the call; there is little filler.

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 a simple getter with one required parameter and full schema coverage, and the description covers the endpoint and auth scope. However, with no output schema, it would be stronger if it briefly described what 'user info' is returned (e.g., ID, name, account status), which an agent may need to decide whether this is the right call.

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 (locationId) and schema description coverage is 100%, with the schema itself saying 'Location identifier'. The description does not add any further meaning (e.g., format or where to obtain the location ID), so the baseline 3 is appropriate when the schema carries the parameter documentation.

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 verb ('Get'/'Retrieve') and a specific resource ('current LinkedIn user' / 'authenticated LinkedIn user info for a location'). The 'LinkedIn' qualifier distinguishes it from sibling tools like ghl_ad_fb_current_user_get and ghl_ad_google_current_user_get without needing to name them.

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?

The phrase 'for a location' implies the tool is scoped to a location, and 'authenticated LinkedIn user' implies it should be used when the current LinkedIn identity is needed. However, there is no explicit 'use this when...' guidance, no exclusions, and no named alternatives for retrieving user info from other ad platforms.

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