Skip to main content
Glama
LinkedIn Ads MCP Server

LinkedIn Ads MCP Server

by get-mcp-ads

linkedin get insights

linkedin_get_insights
Read-onlyIdempotent

Generates LinkedIn Ads performance reports grouped by a single pivot, any date granularity, and up to 20 fields. Computes CTR, CPC, and CPM from raw metrics because the API omits ratios.

Instructions

Run a LinkedIn Ads report grouped by one pivot. This is the analytics finder: one pivot, any granularity, and up to 20 fields including dateRange and pivotValues. Ratios such as CTR, CPC and CPM do not exist in the API and are computed here from the raw terms.

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>",
      "startDate": "<startDate>"
    },
    "name": "linkedin_get_insights"
  }
}

Input Schema

NameRequiredDescriptionDefault
pivotNoGrouping. Defaults to CAMPAIGN. One of: ACCOUNT, CAMPAIGN_GROUP, CAMPAIGN, CREATIVE, COMPANY, SHARE, CONVERSION, MEMBER_COMPANY, MEMBER_COMPANY_SIZE, MEMBER_INDUSTRY, MEMBER_SENIORITY, MEMBER_JOB_TITLE, MEMBER_JOB_FUNCTION, MEMBER_COUNTRY_V2, MEMBER_REGION_V2, MEMBER_COUNTY, SERVING_LOCATION, PLACEMENT_NAME, IMPRESSION_DEVICE_TYPE, EVENT_STAGE, CARD_INDEX, CONVERSATION_NODE, CONVERSATION_NODE_OPTION_INDEX.
endDateNoInclusive end, YYYY-MM-DD. Defaults to today.
metricsNoMetric keys from linkedin://metrics. Defaults to spend, impressions, clicks and the ratios.
sortFieldNoNative field used to order the returned rows.
sortOrderNoAscending or descending native result ordering.
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.
timeGranularityNoDefaults to ALL, one row for the whole range.
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

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower. The description adds genuinely non-structured behavior: ratios like CTR, CPC and CPM are not API-native and are computed here from raw terms, which explains why returned fields may include values absent from the metrics vocabulary. It omits row limits and pagination behavior for a report tool.

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?

Three short sentences with the core action front-loaded and no filler. The computed-ratios sentence earns its place; the middle sentence is somewhat redundant with the first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 12 parameters at full schema coverage, rich annotations, and an output schema that documents return values, the description need only cover purpose and the non-obvious computed-metrics behavior, both of which it does. The unresolved sibling ambiguity is scored under usage guidelines rather than completeness.

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 carries parameter documentation and the baseline is 3. The description adds only loose framing ("one pivot, any granularity"), and its claim of "up to 20 fields" conflicts with the schema's maxItems: 40 for metrics, which could mislead about capacity; note this is a schema inconsistency, not an annotation contradiction.

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: "Run a LinkedIn Ads report grouped by one pivot," and adds a scoping phrase ("the analytics finder"). It distinguishes this from entity-listing siblings, but does not name or distinguish it from linkedin_run_statistics_report or linkedin_get_demographics, which occupy overlapping territory.

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?

Usage is implied rather than stated: "one pivot, any granularity" tells the agent the shape of appropriate requests. There is no explicit when-to-use/when-not guidance and no routing rule pointing to linkedin_run_statistics_report or linkedin_get_demographics, so the agent must infer the choice from name alone.

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