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

ghl-mcp-server-v2

by zackscriven

ghl_ad_li_campaign_group_reporting_get

Read-onlyIdempotent

Retrieve reporting metrics for a specific LinkedIn campaign group by providing campaign group ID, location ID, and date range. Access clicks, impressions, cost, CTR, and conversion data.

Instructions

Get campaign group reporting Retrieve reporting metrics for a specific LinkedIn campaign group Endpoint: GET /ad-publishing/linkedin/reporting/campaign-group/{campaignGroupId} (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": {
      "campaignGroupId": "<campaignGroupId>",
      "locationId": "<locationId>",
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "ghl_ad_li_campaign_group_reporting_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoReporting fields. Pass as comma-separated values on the wire (e.g. ?fields=impressions,clicks).
endDateYesEnd date in yyyy-mm-dd format
startDateYesStart date in yyyy-mm-dd format
locationIdYesLocation ID
campaignGroupIdYesCampaign group identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, 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). It stops short of noting rate limits or result cardinality.

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 and scope are front-loaded in the first two lines, with endpoint and auth details relegated to supporting lines. The endpoint/version/source metadata is slightly verbose but earns its place as invocation context.

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?

For a read-only reporting call with fully documented parameters and annotations, most of what an agent needs is present. However, with no output schema, the description gives no hint about the shape of the returned metrics, default fields, or aggregation granularity — leaving the return contract entirely unexplained.

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%, so all five parameters (including the fields enum list and date formats) are already documented in the schema. The description adds no parameter-level meaning beyond the endpoint template showing campaignGroupId as a path segment. 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?

States a specific verb and resource ('Get campaign group reporting', 'Retrieve reporting metrics for a specific LinkedIn campaign group'), which pins the scope to campaign-group level rather than account or campaign level. It never names the nearest siblings (ghl_ad_li_reporting_get, ghl_ad_li_reporting_list, ghl_ad_li_campaign_group_get), so differentiation is inferable but not explicit.

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 endpoint path and platform (LinkedIn) make usage implicit — retrieve metrics for a campaign group — but there is no statement of when to prefer this over ghl_ad_li_reporting_get or ghl_ad_li_reporting_list, nor any prerequisites beyond the OAuth scope. Adequate but leaves the sibling routing to inference.

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