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

flin-linkedin-ads-mcp

by flin-agency

get_share_content

Retrieve LinkedIn share or ugcPost content by URN through the Posts and Images APIs, with optional raw output for inspection.

Instructions

Resolve LinkedIn share/ugcPost content via the Posts and Images APIs. Requires their additional permissions. For ad images prefer get_creative with imageUrl on API 202610+. External image URLs alone cannot bypass dashboard restrictions.

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": {
      "share_urn": "<share_urn>"
    },
    "name": "get_share_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
share_urnYes
include_rawNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • changedInput schema / properties / share_urn / pattern
      Previous value: -"^urn:li:share:[0-9]+$"New value: +"^urn:li:(share|ugcPost):[0-9]+$"
  2. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that additional permissions are required and that external image URLs cannot bypass dashboard restrictions, but it does not explain failure behavior, response contents, or other operational traits.

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 compact and front-loads the core purpose, permissions caveat, and sibling alternative. It is efficient, though some phrasing like 'resolve' could be clearer.

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?

For a two-parameter tool with no annotations and no output schema, the description covers purpose, permissions, restrictions, and an alternative. It still omits what include_raw does and what the call returns, leaving notable gaps for correct invocation.

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 description coverage is 0%, so the description must compensate. It only implicitly relates to share_urn by mentioning share/ugcPost, and it does not mention the include_raw parameter at all, leaving parameter meaning largely undocumented.

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?

The description states a specific verb ('Resolve') and resource ('LinkedIn share/ugcPost content') and names the APIs used. It also distinguishes itself from a sibling by directing ad-image use to get_creative, though 'resolve' remains somewhat jargon-heavy.

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

Usage Guidelines5/5

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

It explicitly states the use case (share/ugcPost content) and names the alternative for ad images: get_creative with imageUrl on API 202610+. This is clear routing guidance with an explicit condition for choosing the sibling.

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