Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get LinkedIn job

linkedin_live_job_get_v2
Read-onlyIdempotent

Retrieve a LinkedIn job posting by numeric job ID or linkedin.com/jobs/view URL to inspect its details for research, tracking, or application planning.

Instructions

Get a LinkedIn job by id. Requires jobId.

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

Input Schema

NameRequiredDescriptionDefault
jobIdYesRequired. LinkedIn job ID as a numeric string, or a linkedin.com/jobs/view/ URL.
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. The description adds nothing beyond that — no mention of behavior when the job ID is invalid or not found, and no note that results reflect live LinkedIn data without caching.

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 list, but the total length is well within reason.

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 simple single-record read tool with full schema coverage and complete annotations, the definition covers the essentials. It falls short on sibling differentiation (batch vs single fetch) and on any indication of failure behavior, which an agent would need to route and recover correctly.

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 jobId's numeric-string-or-URL format, plus context, llm_model, and conversation_id, are already fully documented. The description's brief jobId mention adds no meaning beyond the schema, making the baseline 3 appropriate.

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 states a specific verb and resource ('Get a LinkedIn job by id'), so an agent knows exactly what it fetches. It does not distinguish this from siblings such as linkedin_live_job_batch_v2 or linkedin_live_job_similar_v2, leaving the single-vs-batch choice implicit.

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 guidance on when to use this tool versus the batch, similar, relatedViews, or hiringTeam variants. The sentence 'Requires `jobId`' restates a schema fact rather than describing a usage condition or prerequisite.

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