Skip to main content
Glama

Social Fetch

by io.github.social-freak-ltd
OverviewDiscussionsAdmin

Get LinkedIn job

linkedin_live_job_get_v2
Read-only

Get a LinkedIn job by id.

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

B3.3/5.0
Behavior3/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 little beyond that—no mention of return format, authentication, or external data behavior—but for a simple read-by-id tool this is acceptable. There is no contradiction between the description and 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?

The description is one sentence with zero filler and the core idea is front-loaded. For a simple fetch tool, this is appropriately sized and well structured.

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 minimal and the schema covers parameter formats, but the tool has 13 parameters and no output schema. It does not clarify which of the many linkedin_live_job_* siblings to choose, nor does it describe what the response contains. It is adequate for basic invocation, but not fully complete for an agent navigating a large toolset.

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 schema already documents all parameters, including jobId's format and the alias relationships. The description does not add meaning beyond the schema, but it does not need to; the baseline of 3 applies.

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 clear verb and resource: 'Get a LinkedIn job by id.' This identifies the tool as a single-job fetch and distinguishes it from search/list tools. However, it does not explicitly differentiate it from sibling tools like linkedin_live_job_batch_v2 or linkedin_live_job_similar_v2, relying on the word 'by id' to carry that weight.

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 provides no guidance on when to use this tool versus alternatives. Sibling tools such as linkedin_live_jobs_search_v2, linkedin_live_job_batch_v2, and linkedin_live_job_hiringTeam_v2 are present, but the description does not state that this tool is for retrieving a single job from a known ID, nor does it mention any conditions or exclusions.

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