Skip to main content
Glama
mcp-linkedin-ads

mcp-linkedin-ads

by mharnett

linkedin_ads_account_performance

Retrieve account-level aggregate LinkedIn Ads performance metrics for a date range to produce high-level summaries of spend, clicks, and conversions.

Instructions

Get account-level aggregate performance metrics for a date range. Good for high-level summaries. Note: reach (approximateMemberReach) and the derived frequency field are not populated at pivot=ACCOUNT; query at CAMPAIGN/CAMPAIGN_GROUP via linkedin_ads_campaign_performance or linkedin_ads_analytics if you need reach.

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_account_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.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses a real data caveat (reach/approximateMemberReach and derived frequency are unpopulated at pivot=ACCOUNT), but says nothing about auth requirements, rate limits, row limits, or what the response looks like for a metrics tool with no output schema.

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?

Three tight sentences, front-loaded with the purpose, then the use case, then the caveat and routing. Every sentence carries information an agent needs; nothing is repeated from the schema.

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

Completeness3/5

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

With no annotations and no output schema, the description should say more about what metrics come back and how account_id affects the result. It covers purpose, routing, and the main data limitation well, but leaves the caller guessing about output content and the optional scope parameter.

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%, near the threshold where the schema does the heavy lifting, so baseline 3 applies. The description adds no parameter-level meaning at all: it never mentions account_id (which is optional even though the tool is account-scoped) and only gestures at the date range already documented in the schema.

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 and resource with explicit scope: account-level aggregate performance metrics for a date range. The pivot framing (pivot=ACCOUNT vs CAMPAIGN/CAMPAIGN_GROUP) distinguishes it concretely from linkedin_ads_campaign_performance and linkedin_ads_analytics.

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?

Gives a positive use case ("Good for high-level summaries") and an explicit when-not plus named alternatives for the reach/frequency case. It doesn't cover other selection criteria, such as when to choose all three time granularities or when analytics is preferred for non-reach needs, so it falls short of a full 5.

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