Skip to main content
Glama
Sign In
@isteam/linkedin-mcp

@isteam/linkedin-mcp

by isteamhq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_article_post

Post an article link on LinkedIn with your commentary. Customize the article card using optional title and description to drive engagement.

Instructions

Share an article link on LinkedIn with commentary

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": {
      "text": "<text>",
      "article_url": "<article_url>"
    },
    "name": "create_article_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesCommentary text for the article share
article_urlYesURL of the article to share
article_titleNoTitle for the article card
article_descriptionNoDescription for the article card

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so description bears full burden. It lacks disclosure of side effects (e.g., public posting), authentication requirements, or rate limits. Minimal behavioral context beyond the basic action.

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?

Single sentence, 8 words, no fluff. Every word carries meaning. Appropriately concise for the tool's simplicity.

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?

Despite simplicity, the description omits important context: how article card fields (title, description) interact, URL validation, and posting behavior. For a social media post tool, more detail is needed.

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 baseline is 3. The description adds minimal value beyond schema; 'commentary' and 'article share' are implied. No additional format or usage details.

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 clearly states the action ('share'), resource ('article link'), and context ('on LinkedIn with commentary'). It distinguishes from sibling tools like create_post (generic post) and comment_on_post, though not explicitly.

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 on when to use this tool versus alternatives (e.g., create_post, comment_on_post). No prerequisites or conditions provided.

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

Deploy Server

Other Tools