LinkedIn Ads MCP Server

get_creative

Retrieve details of a specific ad creative by providing its unique ID. Access key attributes including format, status, and associated campaign.

Instructions

Get details of a single creative by ID.

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": {
      "id": "<id>"
    },
    "name": "get_creative"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 3, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description must fully disclose behavior. It only states that the tool 'gets details,' implying a read operation, but fails to specify whether it is read-only, any permission requirements, or side effects. The lack of output schema leaves the agent uninformed about the response structure.

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?

The description is a single, front-loaded sentence with no extraneous information. However, it could be slightly expanded to include useful details without losing conciseness.

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

Completeness2/5

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

Given the presence of sibling tools (e.g., 'list_creatives', 'get_creative_analytics') and no output schema, the description is incomplete. It does not clarify what 'details' are returned, how the ID is obtained, or when to prefer this over other tools. A more complete description would specify the return fields or link to list_creatives.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The only parameter 'id' has 0% schema description coverage, and the tool description merely mentions 'by ID' without adding format, source, or usage context. This adds minimal meaning beyond the schema's requirement that 'id' is a required string.

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 clearly states 'Get details of a single creative by ID,' using a specific verb ('get') and resource ('creative') with explicit input method (by ID). This distinguishes it from sibling tools like 'list_creatives' (which lists multiple) and 'get_creative_analytics' (which gets analytics).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives such as 'list_creatives' (for browsing) or 'get_creative_analytics' (for performance data). The description does not mention any conditions, prerequisites, or exclusions.

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