Skip to main content
Glama
Sign In

LinkMCP: hosted LinkedIn MCP server

by io.linkmcp
OverviewDiscussionsAdmin

Get My Engagement Activity

linkedin_get_my_engagement
Read-onlyIdempotent

List your own LinkedIn engagement activity (most recent first): comments you wrote (type "comments") or reactions you gave (type "reactions"). Every item carries the permalink of the engaged post (postUrl + activityUrn) - pass either to linkedin_get_post_comments / linkedin_get_post_reactions to see who else engaged. For comments, commentId can be used as parentCommentId in linkedin_get_nested_comments to list replies to your comment; for reactions left on a comment, commentId identifies the comment you reacted to. Paginate by passing the returned cursor back with the same type (cursors are type-specific; the final page may be empty).

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": {
      "type": "<type>"
    },
    "name": "linkedin_get_my_engagement"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesWhich engagement activity to list: "comments" (comments you wrote) or "reactions" (reactions you gave).
limitNoItems per page (1-100). Defaults to 20.
cursorNoPagination cursor from a previous response of the same type.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely non-obvious behavior beyond that: results are newest-first, cursors are type-specific, and the final page may be empty — all of which affect correct pagination.

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?

Dense but front-loaded: the purpose comes first, then the cross-tool linkage, then pagination notes. Every sentence carries actionable information, though the cross-reference chain makes it longer than strictly minimal.

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

Completeness5/5

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

With no output schema, the description compensates by naming the returned identifiers (postUrl, activityUrn, commentId) and their downstream uses, plus pagination behavior. An agent has everything needed to call it and consume the result correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description still adds meaning the schema does not carry: cursors must be replayed with the same 'type' because they are type-specific, and commentId has distinct cross-tool semantics depending on whether the item is a comment or a reaction.

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?

States a specific verb and resource ('List your own LinkedIn engagement activity') and immediately narrows scope to the two activity types, with 'most recent first' ordering. It is clearly distinguished from siblings like linkedin_get_post_comments and linkedin_get_post_reactions, which concern other people's engagement rather than your own.

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?

Explicitly routes the agent: pass postUrl/activityUrn to linkedin_get_post_comments or linkedin_get_post_reactions, and use commentId as parentCommentId in linkedin_get_nested_comments to list replies. It names both the alternative tools and the exact condition/data that selects them.

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

All LinkMCP: hosted LinkedIn MCP server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources