Skip to main content
Glama
LinkedIn Ads MCP Server

LinkedIn Ads MCP Server

by get-mcp-ads

linkedin validate query

linkedin_validate_query
Read-onlyIdempotent

Checks pivots and metrics against LinkedIn reporting rules before an API call, returning fields sent, dropped, and the 20-field limit status without contacting LinkedIn.

Instructions

Check a pivot and metric combination against the LinkedIn reporting rules before spending a call on it. Returns the fields that would actually be sent, the ones LinkedIn would drop, and the twenty field ceiling. Makes no request to LinkedIn.

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": {
      "pivots": "<pivots>",
      "metrics": "<metrics>"
    },
    "name": "linkedin_validate_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
pivotsYesOne to three pivots, as a report would group them.
endDateNoInclusive end, YYYY-MM-DD. Defaults to today.
metricsYesMetric keys from linkedin://metrics.
startDateNoInclusive start, YYYY-MM-DD. Defaults to 30 days ago.
timeGranularityNoNative reporting aggregation interval. Defaults to ALL.

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. Changed5 schema fields changedv1.0.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / endDate / $ref
      Removed value: -"#/properties/startDate"
    • addedInput schema / properties / endDate / pattern
      Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
    • addedInput schema / properties / endDate / type
      Added value: +"string"
    • 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/5.0
Behavior5/5

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

While annotations cover safety hints (readOnlyHint), the description provides unique behavioral context regarding the output: specifically listing that it returns 'the fields that would actually be sent, the ones LinkedIn would drop, and the twenty field ceiling.'

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?

The description is highly concise and well-structured. The core function is front-loaded, and the critical operational constraint ('Makes no request to LinkedIn') is used as a powerful concluding statement.

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?

The definition is complete for a validation tool, covering the 'why' (reporting rules), the 'what' (pivots/metrics), the operational constraint (no API call), and the nature of the results.

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%, meaning the schema handles the vast majority of semantic definition. The description primarily restates the nature of the inputs (pivot/metric) rather than adding unique semantic meaning beyond the schema's constraints.

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?

The description uses a specific verb ('Check') and resource ('pivot and metric combination') and immediately distinguishes its purpose: validating against LinkedIn reporting rules before using other tools.

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?

It provides clear usage context by advising the user to run it 'before spending a call on it' and explicitly states that it makes 'no request to LinkedIn,' implying its use as a pre-flight safety check against fetch tools.

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