Skip to main content
Glama
mcp-linkedin-ads

mcp-linkedin-ads

by mharnett

linkedin_ads_campaign_performance

Retrieve campaign-level LinkedIn Ads performance metrics—impressions, clicks, spend, conversions, leads, reach, and frequency—for a specified date range to support weekly reporting.

Instructions

Get campaign-level performance metrics (impressions, clicks, spend, conversions, leads, engagement, video views, reach, frequency) for a date range. Reach = approximateMemberReach (unique members exposed); frequency = impressions / reach (computed server-side). This is the main reporting tool for weekly slides.

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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "linkedin_ads_campaign_performance"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateYesEnd date YYYY-MM-DD
account_idNo
start_dateYesStart date YYYY-MM-DD
time_granularityNoALL (default), DAILY, or MONTHLY

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden; it usefully discloses that reach is approximateMemberReach and frequency is computed server-side, but says nothing about permissions, pagination, row limits, or empty-data behavior.

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-loads the core purpose in the first clause, then defines the two derived metrics compactly; every sentence carries information, with only the 'weekly slides' aside being marginally incidental.

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 four-parameter, no-output-schema reporting tool, the description enumerates the returned metrics and explains derived fields, which is close to sufficient; only the meaning of account_id and the effect of time_granularity on result shape remain unaddressed.

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 75% with start/end date and time_granularity already documented; the description adds no meaning to account_id (undocumented in schema) or to the enum values, so it does not compensate for the remaining gap.

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 ('Get campaign-level performance metrics') and enumerates the metric families returned, which clearly distinguishes it from account-level and listing siblings even though no sibling is named.

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?

Adds a concrete usage context ('main reporting tool for weekly slides') that implies when to reach for it, but gives no explicit exclusions or guidance on when to prefer account-level or analytics siblings.

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