Skip to main content
Glama

Social Fetch

by io.github.social-freak-ltd
OverviewDiscussionsAdmin

List LinkedIn profile posts

linkedin_live_person_posts_v2
Read-only

List posts from a LinkedIn person. Accepts a entity id. Returns a list (use cursor when paginated).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
trimNoIgnored if this tool does not support it.
limitNoIgnored if this tool does not support it.
startNo
cursorNo
offsetNoIgnored if this tool does not support it.
contextYesDescribe the user's underlying goal in one sentence — not the tool you are calling.
entityIdNoLinkedIn person entity ID. Not a vanity handle.
pageSizeNoIgnored if this tool does not support it.
entity_idNoAlias for `entityId`. Prefer `entityId`.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
maxResultsNoIgnored if this tool does not support it.
max_resultsNoIgnored if this tool does not support it.
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. Changed8 schema fields changed
    • addedInput schema / properties / entity_id / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]
    • removedInput schema / properties / entity_id / type
      Removed value: -"string"
    • addedInput schema / properties / limit
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}
    • addedInput schema / properties / maxResults
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}
    • addedInput schema / properties / max_results
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}
    • addedInput schema / properties / pageSize
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}
    • addedInput schema / properties / trim
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / entity_id
      Added value: +{
+  "description": "Alias for `entityId`. Prefer `entityId`.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "entityId",
-  "context",
-  "llm_model"
-]New value: +[
+  "context",
+  "llm_model"
+]
  3. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds useful behavioral context by stating the return type and pagination approach, but does not disclose other traits like output fields, ordering, rate limits, or open-world caveats. This is adequate but minimal.

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?

Two short sentences with no filler: purpose, required input type, and pagination behavior are all front-loaded. Every sentence earns its place despite the minor grammatical typo 'a entity id.'

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?

The description covers the core use case and pagination, which is important given there is no output schema. However, with 13 parameters and many sibling list/resolve tools, it could usefully mention that entityId is effectively required, how to obtain it (e.g., via a resolve tool), and what each returned post contains. It is sufficient but not complete.

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 85%, so the schema carries most parameter meaning. The description adds a little by identifying the entity ID as the key input and by explaining cursor usage, but it does not enrich the many generic 'Ignored if this tool does not support it' parameters. Baseline 3 is appropriate.

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?

The description clearly states the action and resource: 'List posts from a LinkedIn person.' This distinguishes it from sibling tools like linkedin_company_posts_v2 and linkedin_posts_search_list. Including the return type ('Returns a list') further sharpens the purpose.

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 implies when to use it: when you have a LinkedIn person's entity ID and want their posts. It gives a prerequisite ('Accepts a entity id') and pagination guidance ('use cursor when paginated'), but does not explicitly name alternatives or exclusions, such as using linkedin_live_person_resolve_v2 when only a vanity handle is available.

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

All Social Fetch 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