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

ghl-mcp-server-v2

by zackscriven

ghl_ad_li_campaign_group_get

Read-onlyIdempotent

Retrieve a LinkedIn ad campaign group by ID and location ID to inspect its campaign details.

Instructions

Get ad campaign group Retrieve a LinkedIn ad campaign group by ID Endpoint: GET /ad-publishing/linkedin/ads/{adId} (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": {
      "adId": "<adId>",
      "locationId": "<locationId>"
    },
    "name": "ghl_ad_li_campaign_group_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
adIdYesAd identifier
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, destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the required OAuth scope 'adPublishing.readonly' and the API version header 'v3', which help an agent diagnose auth failures.

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 definition is front-loaded: name-level purpose first, then a one-line summary, then endpoint and scope metadata. The endpoint/version/source lines are operational metadata rather than pure prose, but they are compact and each line carries distinct 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 simple two-parameter read with full annotation coverage and no output schema, the description supplies everything needed to invoke it, including auth scope. The only gap is the ambiguous resource naming in the URL versus the tool name, and no hint of what object shape comes back.

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?

Schema description coverage is 100% with only two required parameters (adId, locationId), both documented in the schema itself. The description adds no semantics about what adId refers to (an ad vs. a campaign group id is genuinely ambiguous here) or how locationId scopes the lookup, so the baseline 3 is appropriate.

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 uses a specific verb and resource ('Retrieve a LinkedIn ad campaign group by ID'), which clearly separates it from siblings like ghl_ad_li_campaign_group_upsert or _publish. The only blemish is that the endpoint path it cites is '/ad-publishing/linkedin/ads/{adId}', which reads as an ad rather than a campaign group and could confuse an agent about the resource.

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 'by ID' implies this is a single-record fetch that requires a known identifier, which is a weak usage signal. It never states when to prefer this over listing or reporting siblings such as ghl_ad_li_campaign_group_reporting_get, nor does it mention prerequisites or exclusions.

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