Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get LinkedIn activity

linkedin_live_activity_get_v2
Read-onlyIdempotent

Retrieve a LinkedIn activity by its activity ID to inspect or verify a specific post or interaction.

Instructions

Get a LinkedIn activity by id. Requires activityId.

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": {
      "activityId": "<activityId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "linkedin_live_activity_get_v2"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
activityIdYesLinkedIn activity ID.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered structurally. The description adds nothing beyond that — it does not explain that this is a single-entity fetch returning one activity object, nor does it acknowledge the conversation_id handshake required by the schema. Credit for the clear read semantics, but the description itself contributes almost no behavioral context.

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?

Two short sentences, front-loaded with the primary action, with no filler. The second sentence is largely redundant with the schema's required list, costing it a point, but the overall size is appropriate for a simple retrieval tool.

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 read-only single-entity fetch with no output schema and fully documented parameters, the description is minimally adequate. However, an agent gets no sense of what an 'activity' contains (post? share? comment?) or the approximate shape of the response, which would help it decide between this and the activity sub-resource siblings.

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 all four parameters (including context, llm_model, conversation_id) are already documented in the schema. The description only repeats that activityId is required, which the schema's required list already states, so no additional meaning is conveyed. Baseline 3 applies.

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 names a specific verb and resource — 'Get a LinkedIn activity by id' — so an agent knows exactly what is retrieved. It does not differentiate from the closely related siblings such as linkedin_live_activity_comments_v2 or linkedin_live_activity_reactions_v2, which also operate on LinkedIn activities, leaving it slightly short of a 5.

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?

There is no when-to-use guidance, no exclusions, and no pointer to the comment/reaction sibling tools that operate on the same activity IDs. The only conditioning sentence is a restatement of the required parameter, which is not usage guidance.

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