Skip to main content
Glama
LinkedIn Ads MCP Server

LinkedIn Ads MCP Server

by get-mcp-ads

linkedin list ad creatives

linkedin_list_ad_creatives
Read-onlyIdempotent

List the images and playable videos used by an account's LinkedIn ads, showing actual ad names and separating landing URLs from media URLs.

Instructions

List the images and playable videos used by the ads of an account, with the actual ad names. Separates landing URLs from media URLs. Does not report delivery.

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

Input Schema

NameRequiredDescriptionDefault
adIdsNoExact ad IDs to resolve instead of listing a page, up to ten.
limitNoMaximum ads scanned in this page; inspect coverage for additional data.
pageTokenNoOpaque nextPageToken from the preceding response; omit for the first page.
adAccountIdYesSelected LinkedIn advertising account, numeric ID. It must be listed in LINKEDIN_ADS_ACCOUNT_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 declare this is a read-only, idempotent, open-world, non-destructive call. The description adds real value on top: it says the result pairs creatives with actual ad names, splits landing URLs from media URLs, and explicitly excludes delivery metrics. A note on pagination via pageToken/coverage would have made it a 5.

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 short sentences, each earning its place: what it lists, how it structures URLs, and what it deliberately omits. The key scope statement is front-loaded and there is no filler.

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?

With an output schema present and full annotation coverage, the description need only frame scope and exclusions, which it does. The remaining gap is sibling disambiguation against linkedin_get_creatives and linkedin_list_media, which matters in a tool family this dense.

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 adIds, limit, pageToken, and adAccountId are all fully documented in the schema, including the maxItems of 10 and the account allowlist requirement. The description adds no parameter-level detail (such as the adIds exact-resolve mode versus paging), so baseline 3 applies.

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 (list) and resource (images and playable videos used by ads of an account), plus the notable detail that ad names are included and landing URLs are separated from media URLs. It does not explicitly distinguish itself from the sibling linkedin_get_creatives or linkedin_list_media, which an agent could easily confuse it with.

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?

The exclusion 'Does not report delivery' implicitly routes delivery questions to linkedin_get_delivery_status, and 'list a page' (in the schema) implies adIds is the targeted lookup path. But there is no explicit statement of when to pick this over linkedin_get_creatives or linkedin_list_media, so the agent must infer the boundary.

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