Skip to main content
Glama
flin-linkedin-ads-mcp

flin-linkedin-ads-mcp

by flin-agency

get_creative

Retrieve a LinkedIn ad creative by ID and request its image URL or metadata via CreativeMetadata API 202610+, enabling visual asset access without Posts permissions. External image URLs may expire.

Instructions

Fetch one creative by id. Request fields imageUrl or metadata for the visual asset URL via CreativeMetadata on API 202610+, without needing Posts access. Image URLs are external and may expire.

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

NameRequiredDescriptionDefault
idYes
fieldsNo
ad_account_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.1/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It adds real behavioral context — no Posts access required, API-version gating for CreativeMetadata, and that returned image URLs are external and may expire — but it never states auth scope beyond that, whether ad_account_id is required, or anything about error behavior for invalid ids.

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?

Three sentences, front-loaded with the core action, then the fields/version caveat, then the URL-expiry warning. Every sentence carries information, though the version/API-suffix phrasing is dense enough to slow a first read.

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?

There is no output schema, no annotations, and 0% parameter coverage, so the description is the only source of truth — yet it never describes the response shape for a creative object or explains ad_account_id. For a three-parameter fetch with an unconstrained `fields` array whose allowed values are undocumented, this leaves too much to guesswork.

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?

Schema coverage is 0%, so the description must explain all three parameters. It meaningfully explains `fields` (pass imageUrl or metadata to get the asset URL) and implies `id`, but `ad_account_id` is never mentioned at all — neither its purpose nor whether it is optional — leaving a third of the interface undocumented anywhere.

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?

"Fetch one creative by id" is a specific verb+resource and the singular "one" distinguishes it from list_creatives. However, it never contrasts with get_creative_media, which a reader would expect to be the natural alternative for retrieving image assets, so the agent has to infer the boundary.

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 description does give scenario hints: request imageUrl/metadata when you want the visual asset URL via CreativeMetadata on API 202610+, and it notes this avoids needing Posts access. That is useful context but there is no explicit when-not or named alternative, so the usage boundary against get_creative_media and list_creatives is only implied.

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