Skip to main content
Glama

Social Fetch

by io.github.social-freak-ltd
OverviewDiscussionsAdmin

List related LinkedIn jobs

linkedin_live_job_relatedViews_v2
Read-only

List related jobs for a LinkedIn job. Accepts a job id. Returns a list (use cursor when paginated).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
trimNoIgnored if this tool does not support it.
jobIdNoLinkedIn job ID as a numeric string, or a linkedin.com/jobs/view/ URL.
limitNoIgnored if this tool does not support it.
jobUrlNoAlias for `jobId`. Prefer `jobId`.
offsetNoIgnored if this tool does not support it.
contextYesDescribe the user's underlying goal in one sentence — not the tool you are calling.
job_urlNoAlias for `jobId`. Prefer `jobId`.
pageSizeNoIgnored if this tool does not support it.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
maxResultsNoIgnored if this tool does not support it.
max_resultsNoIgnored if this tool does not support it.
linkedinJobUrlNoAlias for `jobId`. Prefer `jobId`.
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. Changed12 schema fields changed
    • addedInput schema / properties / jobUrl / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]
    • removedInput schema / properties / jobUrl / type
      Removed value: -"string"
    • addedInput schema / properties / job_url / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]
    • removedInput schema / properties / job_url / type
      Removed value: -"string"
    • addedInput schema / properties / limit
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}
    • addedInput schema / properties / linkedinJobUrl / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  }
+]
    • removedInput schema / properties / linkedinJobUrl / type
      Removed value: -"string"
    • addedInput schema / properties / maxResults
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}
    • addedInput schema / properties / max_results
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}
    • addedInput schema / properties / pageSize
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}
    • addedInput schema / properties / trim
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}
  2. Changed6 schema fields changed
    • changedInput schema / properties / jobId / description
      Previous value: -"LinkedIn job ID."New value: +"LinkedIn job ID as a numeric string, or a linkedin.com/jobs/view/ URL."
    • removedInput schema / properties / jobId / pattern
      Removed value: -"^\\d+$"
    • addedInput schema / properties / jobUrl
      Added value: +{
+  "description": "Alias for `jobId`. Prefer `jobId`.",
+  "type": "string"
+}
    • addedInput schema / properties / job_url
      Added value: +{
+  "description": "Alias for `jobId`. Prefer `jobId`.",
+  "type": "string"
+}
    • addedInput schema / properties / linkedinJobUrl
      Added value: +{
+  "description": "Alias for `jobId`. Prefer `jobId`.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "jobId",
-  "context",
-  "llm_model"
-]New value: +[
+  "context",
+  "llm_model"
+]
  3. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavior beyond that: it returns a list and instructs the agent to use a cursor when paginating. No contradiction with annotations.

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, purposeful sentences with no filler. The operation, input, output type, and pagination hint are all front-loaded and each sentence earns its place.

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?

The description is adequate for a simple read tool, but gaps remain: it does not specify which parameter drives cursor pagination, does not describe the shape of the returned related-jobs list (and there is no output schema), and does not disambiguate from linkedin_live_job_similar_v2. Required parameters are covered by the schema, so that is not a gap.

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 the baseline is 3. The description only mentions "job id" conceptually and "cursor" without mapping to a specific parameter; the schema already documents jobId, its aliases, and pagination-related fields. The description adds little semantic value over the schema.

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 clearly states a specific verb and resource: "List related jobs for a LinkedIn job," and clarifies it accepts a job id. However, it does not differentiate itself from the near-synonymous sibling linkedin_live_job_similar_v2, so an agent cannot tell the two apart from the description alone.

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?

The description gives no guidance on when to use this tool versus alternatives. It names no exclusions, prerequisites, or competing tools, which is a meaningful gap given the existence of linkedin_live_job_similar_v2.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Social Fetch toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources