Skip to main content
Glama
LinkedIn Ads MCP Server

LinkedIn Ads MCP Server

by get-mcp-ads

linkedin get demographics

linkedin_get_demographics
Read-onlyIdempotent

Breaks down LinkedIn ad delivery by professional demographics like company, industry, seniority, job title, or location to analyze campaign performance.

Instructions

Break LinkedIn delivery down by professional demographics: company, company size, industry, seniority, job title, job function or location. These are the numbers LinkedIn is bought for, and they come with limits the tool states alongside the rows.

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

Input Schema

NameRequiredDescriptionDefault
limitNoKeep only the top rows by impressions. Defaults to 50.
endDateNoInclusive end, YYYY-MM-DD. Defaults to today.
metricsNoDefaults to spend, impressions, clicks and CTR. Conversion value, carousel and reach fields are not available here.
breakdownYesWhich professional demographic to group by.
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.
resolveNamesNoResolve the returned URNs to readable names. On by default.
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.5/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. The description adds only that limits are stated alongside rows, without specifying what those limits are or any auth/rate-limit detail. It does not contradict the annotations.

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?

Two sentences, with the purpose front-loaded. The second sentence mixes useful context ('limits ... alongside the rows') with promotional filler ('numbers LinkedIn is bought for'), so it is concise but not waste-free.

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?

For a read-only reporting tool with full schema coverage, annotations, and an output schema, the description gives enough to identify the breakdown capability. It omits comparison guidance to sibling reporting tools, which keeps it from a 5.

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 the baseline is 3. The description's list of demographic categories loosely maps to the breakdown enum, but it does not add syntax or meaning for limit, metrics, campaign filters, resolveNames, or dates beyond the schema.

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: break LinkedIn delivery down by professional demographics, and lists the available grouping categories. It does not explicitly distinguish this from sibling reporting tools such as linkedin_get_insights or linkedin_run_statistics_report, so it falls short of a 5.

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?

Implies the tool is for demographic breakdown reporting by naming the professional demographic dimensions. It gives no explicit when-to-use guidance, alternatives, or exclusions compared with sibling reporting tools; 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.