Skip to main content
Glama

Social Fetch

by io.github.social-freak-ltd
OverviewDiscussionsAdmin

Get LinkedIn recommendations

linkedin_live_person_recommendations_v2
Read-only

Get recommendations for 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.
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

B3.2/5.0
Behavior3/5

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

The description discloses that the tool returns a list and uses cursor-based pagination, which adds value beyond the readOnlyHint and openWorldHint annotations. However, it does not explain the nature of the recommendations, potential rate limits, or how the cursor is supplied (via a parameter). With annotations already covering safety, this is a modest addition.

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?

The description is two concise sentences with no filler. The core purpose is front-loaded, and the pagination note is useful. Every word earns its place.

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?

Given the tool has 11 parameters, no output schema, and many siblings, the description is insufficient. It does not explain what 'recommendations' are, what fields the returned list contains, how to obtain a cursor, or which pagination parameter to use. The generic parameter descriptions add confusion. An agent would struggle to invoke this tool correctly without additional context.

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?

The schema describes all parameters (100% coverage), but many have generic descriptions like 'Ignored if this tool does not support it.' The description mentions 'entity id' and pagination, which loosely aligns with entityId and pagination parameters, but it does not clarify which pagination parameter to use (cursor vs offset/limit) or the meaning of the generic optional params. Baseline 3 is appropriate since schema covers the basics.

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 tool returns recommendations for a LinkedIn person and accepts an entity ID. It is a specific verb+resource and mentions pagination. However, it does not differentiate from sibling tools like linkedin_live_person_similar_v2, which could also return related people, so it is not fully distinct.

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?

The description provides no guidance on when to use this tool versus alternatives such as person_similar, people_search, or person_resolve. It implicitly requires an entity ID but does not explain how to obtain one or when recommendations are preferable. No exclusions or alternative names are given.

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