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

ghl-mcp-server-v2

by zackscriven

ghl_ad_li_integration_get

Read-onlyIdempotent

Retrieve LinkedIn Ads integration details for a location to verify ad publishing configuration and connection status.

Instructions

Get LinkedIn integration Retrieve the LinkedIn Ads integration details for a location Endpoint: GET /ad-publishing/linkedin/integration (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_integration_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.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), and the description adds useful context beyond them: the exact endpoint, the version header, and the required adPublishing.readonly OAuth scope. It does not describe error behavior when no integration is connected, but the auth and endpoint details are solid added value.

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 short and front-loads the purpose before the endpoint metadata. The opening line "Get LinkedIn integration" largely restates the title and the name, and the source file path is internal metadata of marginal value, but neither is harmful.

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 single-parameter read tool, the description plus rich annotations and fully documented schema give an agent enough to invoke it correctly. It does not say what the returned integration details contain, but for a simple lookup with annotations already covering safety and idempotency, that omission is minor.

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 a single required parameter with 100% schema description coverage, so the schema already explains locationId as "Location identifier." The description's phrase "for a location" reinforces that meaning but adds no format, constraints, or syntax beyond what the schema provides, so the baseline 3 is appropriate.

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 names a specific verb ("Retrieve") and a specific resource ("LinkedIn Ads integration details") scoped to a location, which cleanly distinguishes it from the LinkedIn create sibling and from the Facebook/Google integration getters. An agent can identify the operation without opening the schema.

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 only implied by "Retrieve... for a location"; there is no explicit when-to-use guidance, no exclusions, and no routing against alternatives such as ghl_ad_li_integration_create or the other platform integration getters. The OAuth scope line hints at a prerequisite but is not framed as usage guidance.

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