Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List related LinkedIn jobs

linkedin_live_job_relatedViews_v2
Read-onlyIdempotent

List related LinkedIn jobs by job ID or jobs/view URL to discover similar roles and broaden a job search. Provide a job ID and get a list of related job results.

Instructions

List related jobs for a LinkedIn job. Requires jobId. Returns a list.

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_relatedViews_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

B3.1/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 covered. The description adds only 'Returns a list', with no indication of result count, pagination, ordering, or what 'related' is based on, and there is no output schema to fill that gap.

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?

Three short sentences, front-loaded with the action and the prerequisite, with zero filler. Nothing could be removed without losing information.

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 low-complexity read tool with fully documented parameters and a complete annotation set, this is close to adequate. The meaningful omissions are the relationship to the similar/related sibling and any sense of result size or pagination, which an agent would need before calling it.

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 coverage is 100% and each parameter (jobId, context, llm_model, conversation_id) carries its own documentation, so the schema does the heavy lifting. The description merely repeats that jobId is required and adds no format, constraint, or usage nuance beyond it.

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 ('List related jobs for a LinkedIn job'), which is far better than restating the title. It does not, however, distinguish itself from the closely-scoped sibling linkedin_live_job_similar_v2, leaving an agent to guess which of the two yields which relation.

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?

'Requires `jobId`' is a prerequisite, not usage guidance. There is no statement of when to pick this over job_similar_v2, job_get_v2, or jobs_search_v2, and no exclusions or conditions.

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