Skip to main content
Glama
LinkedIn Ads MCP Server

LinkedIn Ads MCP Server

by get-mcp-ads

linkedin run statistics report

linkedin_run_statistics_report
Read-onlyIdempotent

Generate LinkedIn Ads statistics by cross-pivoting up to three dimensions in a single request. Easily analyze metrics by campaign vs. device or campaign group vs. serving location.

Instructions

Run a LinkedIn Ads report grouped by up to three pivots at once. This is the statistics finder, the only way to cross campaign with device, or campaign group with serving location, in a single request.

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": {
      "adAccountId": "<adAccountId>",
      "pivots": "<pivots>",
      "startDate": "<startDate>"
    },
    "name": "linkedin_run_statistics_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
pivotsYesOne to three pivots. Order decides the order of pivotValues.
endDateNoInclusive end, YYYY-MM-DD. Defaults to today.
metricsNoMetric keys from linkedin://metrics. Defaults to spend, impressions, clicks and the ratios.
startDateYesInclusive start, YYYY-MM-DD.
adAccountIdYesSelected LinkedIn advertising account, numeric ID. It must be listed in LINKEDIN_ADS_ACCOUNT_IDS.
campaignIdsNoRestrict reporting to these campaign IDs or URNs in the selected account.
creativeIdsNoRestrict reporting to these owned creative IDs.
campaignTypeNoNative campaign format filter.
objectiveTypeNoNative campaign objective filter.
timeGranularityNoNative reporting aggregation interval. Defaults to ALL.
campaignGroupIdsNoRestrict reporting to these owned campaign-group IDs.

Output Schema

NameRequiredDescriptionDefault
resultYesOriginal tool result: parsed JSON when the text is JSON, otherwise the text. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / properties / result / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "properties": {},
      -    "type": "object"
      -  },
      -  {
      -    "items": {},
      -    "type": "array"
      -  },
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {},
      +    "type": "object"
      +  },
      +  {
      +    "items": {},
      +    "type": "array"
      +  },
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "boolean"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, covering the safety profile. The description adds the behavioral trait that multiple pivots are crossed in a single request, but says nothing about rate limits, async behavior, or the fact that results come from a statistics engine. With annotations doing heavy lifting, this is adequate but not rich.

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?

Two tight sentences with zero waste; the core capability (multi-pivot reporting) is front-loaded before the differentiating detail. Nothing is redundant.

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 100% schema coverage, an output schema, and full annotations, the description only needs to convey the multi-pivot value proposition, which it does. It could be slightly stronger by explicitly contrasting with get_insights/get_demographics, but nothing essential for correct invocation is missing.

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 11 parameters are documented in the schema, including the pivots ordering semantics. The description reinforces the pivot limit ('up to three pivots') but adds no syntax or format detail beyond what the schema already provides. 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?

States a specific verb ('Run') and resource ('LinkedIn Ads report') with a concrete capability: grouping by up to three pivots. It also distinguishes itself from siblings by naming the unique cross-pivot combinations it enables, so an agent can tell it apart from get_insights or get_demographics.

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

Usage Guidelines4/5

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

The description gives a clear trigger for using it — when you need to cross pivots like campaign×device or campaign group×serving location in one request. However, it does not explicitly name the alternative tools to prefer when pivot crossing isn't needed, leaving that routing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.