Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get LinkedIn jobs

linkedin_live_job_batch_v2
Read-onlyIdempotent

Fetch LinkedIn job postings from one or more /jobs/view/ URLs, up to 50 per request, to gather role details across multiple listings.

Instructions

Get LinkedIn jobs 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_job_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.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, covering the safety profile. The description adds nothing beyond that: it does not mention batch fan-out (up to 50 URLs, so partial failures are plausible), rate limiting, or any authentication requirement. Nothing contradicts the annotations, but the added value is minimal.

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 filler. The second sentence is largely redundant with the schema's required-field declaration, which keeps it from a 5, but there is no verbosity to trim.

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 tool with four parameters (three required, including the non-obvious context and llm_model), no output schema, and a batch label in its name, the description is too thin. It omits the multi-URL batch behavior best 50, the conversation_id sequencing requirement is left entirely to the schema, and there is no return-value or failure-mode signal to compensate for the absent output schema.

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 the URL format constraint, context, llm_model, and conversation_id rules, so the schema does the heavy lifting. The description only echoes that `url` is required and adds no syntax, cardinality, or ordering meaning beyond it. Baseline 3 is appropriate for fully documented parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb and resource ("Get LinkedIn jobs by URL"), so the basic intent is legible. However, it never discloses that this is a batch tool accepting up to 50 URLs, nor does it distinguish it from the sibling linkedin_live_job_get_v2, which appears to do a single-job fetch. An agent reading only the description cannot tell the two apart.

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 or when-not-to-use guidance and no mention of alternatives such as the single-job or search siblings. The only guidance is "Requires `url`," which is a restatement of the schema's required field rather than a usage rule.

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