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

ghl-mcp-server-v2

by zackscriven

ghl_ad_li_reporting_list

Read-onlyIdempotent

Retrieve a LinkedIn ad reporting list for campaigns, campaign groups, or ads with selected performance metrics across a specified date range.

Instructions

Get reporting list Retrieve a list of LinkedIn campaigns or campaign groups with reporting data. Deprecated: use GET /ad-publishing/linkedin/reporting/rows with header version: v4. Endpoint: GET /ad-publishing/linkedin/reporting/list (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>",
      "listType": "<listType>",
      "campaignId": "<campaignId>",
      "campaignGroupId": "<campaignGroupId>",
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "ghl_ad_li_reporting_list"
  }
}

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
listTypeYesList type
startDateYesStart date in yyyy-mm-dd format
campaignIdYesCampaign ID
locationIdYesLocation ID
campaignGroupIdYesCampaign group ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • addedInput schema / properties / listType / enum
      Added value: +[
      +  "campaignGroups",
      +  "campaigns",
      +  "ads"
      +]
  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 readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds genuinely new context: the OAuth scope required (adPublishing.readonly), the API version header (v3), and the deprecation status with a successor endpoint.

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?

Front-loaded with the purpose sentence, then deprecation, endpoint, and scopes in a compact block. Slight redundancy between the title line "Get reporting list" and the following sentence, but nothing is wasted overall.

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?

With annotations covering safety, no output schema needed, and full schema coverage, the description supplies what matters: the deprecated status, successor endpoint, version header, and auth scope. The only gap is not mentioning the "ads" list type or what the reporting payload contains.

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%, including per-field descriptions and an enum for listType, so the schema carries the parameter burden. The description adds nothing parameter-specific beyond the general scope, so 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 ("Retrieve a list of LinkedIn campaigns or campaign groups with reporting data") and the LinkedIn qualifier separates it from the FB and Google reporting siblings. However, it omits that the listType enum also supports "ads", so the stated scope is narrower than the tool's actual capability.

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 deprecation notice gives a directional hint (use the /reporting/rows endpoint with v4 header), which is useful usage guidance, but the named alternative is a raw HTTP endpoint rather than a callable sibling, and no condition distinguishes this from ghl_ad_li_reporting_get or ghl_ad_li_campaign_group_reporting_get. Usage is only implied.

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