Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get LinkedIn profiles

linkedin_live_profile_batch_v2
Read-onlyIdempotent

Fetch up to 50 LinkedIn person profiles from profile URLs or handles in one batch request, returning profile data for research, enrichment, or lead qualification.

Instructions

Get LinkedIn person profiles by URL. Requires url.

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

Input Schema

NameRequiredDescriptionDefault
urlYesRequired.
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.
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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered structurally. The description adds nothing behavioral beyond that — it omits the batch semantics (up to 50 URLs per call), any partial-failure behavior when some URLs resolve and others do not, and any rate-limit or credit considerations for a live scraping tool.

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, front-loaded sentences with no padding. The second sentence is largely redundant with the schema's required array, which keeps it just short of a 5.

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?

For a batch tool with four parameters, no output schema, and live external data, the description is too thin. It never states that multiple URLs are accepted in one call or what the response contains per URL, which matters for an agent deciding between one batch call and several single-profile calls.

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%, including detailed guidance for context, llm_model, and conversation_id, so the schema carries the parameter burden. The description's 'Requires `url`' only repeats the required list and adds no syntax or format detail beyond what the url property description already provides.

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 gives a specific verb and resource ('Get LinkedIn person profiles by URL'), which is far more informative than the title alone. However, it never signals that this is the batch variant accepting up to 50 URLs, so an agent cannot distinguish it from the sibling linkedin_live_profile_get_v2 without inspecting the schema.

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 at all — no mention of when to prefer this batch call over the single-profile sibling, over people_search, or over the resolve tool. The only usage statement is 'Requires `url`', which is a restatement of a required field, not 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