Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List similar LinkedIn jobs

linkedin_live_job_similar_v2
Read-onlyIdempotent

Find similar LinkedIn jobs from a job ID or LinkedIn job URL to identify related roles and compare opportunities.

Instructions

List similar LinkedIn jobs. 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_similar_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.8/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 without the description. The description adds only "Returns a list," which conveys nothing about result size, ordering, pagination, or what makes a job "similar" — the details an agent would actually need. No annotation contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded, which is good, but two of the three sentences are redundant: "Requires `jobId`" duplicates the schema and "Returns a list" is near-vacuous. The space could have carried the meaning of "similar" instead.

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?

The tool is conceptually simple, but with no output schema the description is the only place to explain the return shape, and "Returns a list" is insufficient — no indication of result count, pagination, or how similarity is determined. An agent can call it, but cannot predict what it will get back.

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%, and the jobId, context, llm_model and conversation_id parameters are all documented in the schema itself. The description's "Requires `jobId`" merely repeats the schema, so the baseline 3 applies with no added meaning.

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: "List similar LinkedIn jobs," which an agent can distinguish from a generic job lookup. It does not, however, differentiate itself from plausible siblings such as linkedin_live_job_relatedViews_v2 or linkedin_live_job_get_v2, leaving the agent to infer what "similar" means versus those alternatives.

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 named alternative. The only constraint offered is "Requires `jobId`," which is a prerequisite restated from the schema rather than guidance about selecting this tool.

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