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

ghl-mcp-server-v2

by zackscriven

ghl_ad_li_reporting_get

Read-onlyIdempotent

Retrieve LinkedIn Ads analytics data with configurable pivots and time grouping to analyze campaign performance across accounts, campaigns, creatives, and date ranges.

Instructions

Get ad analytics Retrieve LinkedIn Ads analytics data with configurable pivot and time grouping Endpoint: GET /ad-publishing/linkedin/reporting (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>",
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "ghl_ad_li_reporting_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
pivotNoAnalytics pivot typeACCOUNT
fieldsNoReporting fields. Pass as comma-separated values on the wire (e.g. ?fields=impressions,clicks).
endDateYesEnd date in yyyy-mm-dd format
groupByNoTime granularity for analyticsday
startDateYesStart date in yyyy-mm-dd format
entityUrnsNoComma-separated list of entity URNs
locationIdYesLocation ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuine context beyond them: the required OAuth scope (adPublishing.readonly) and the version header (v3), which help the agent understand auth prerequisites. It does not describe return format, keeping it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose, then a clear elaboration, then terse endpoint/version/scope metadata. No wasted sentences; each line adds either purpose or operational 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?

With no output schema, the description should hint at what analytics data is returned, but it does not describe the response shape. It also omits differentiation from the reporting_list sibling. Parameter and safety needs are otherwise covered by schema and annotations.

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 coverage is 100%, so the schema already documents all seven parameters including enums and formats. The description only echoes 'configurable pivot and time grouping,' which maps to pivot/groupBy but adds no syntax or format detail. Baseline 3 is appropriate when the schema carries the load.

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 (Retrieve) and resource (LinkedIn Ads analytics data) with the distinguishing scope of configurable pivot and time grouping. However, it does not clarify how it differs from the closely named sibling ghl_ad_li_reporting_list, leaving the agent to guess between them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance on when to use this versus ghl_ad_li_reporting_list, ghl_ad_li_campaign_group_reporting_get, or other reporting siblings. Usage is only implied by the phrase 'Retrieve LinkedIn Ads analytics data' with no exclusions or selection conditions.

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