Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List LinkedIn hiring team

linkedin_live_job_hiringTeam_v2
Read-onlyIdempotent

Retrieve the hiring team for a LinkedIn job by job ID or URL so you can identify recruiters and decision-makers involved in the role.

Instructions

List the hiring team 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_hiringTeam_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, and openWorldHint, so the safety profile is covered. The description adds essentially nothing beyond that — 'Returns a list' conveys no shape or content, and it omits any note on permissions, rate limits, or what the entries contain.

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?

Three short sentences, front-loaded with the purpose and free of filler. 'Returns a list' is nearly content-free and scrapes against the conciseness standard, but the overall shape is tight.

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?

With no output schema, the description carries the burden of explaining return values, and 'Returns a list' is the bare minimum — it says nothing about fields such as name, title, or profile URL of hiring team members. For a simple read-only list tool this is adequate but leaves a clear 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 jobId, context, llm_model, and conversation_id are all fully documented in the schema. The description's passing mention of jobId adds no syntax or format detail beyond 'numeric string or linkedin.com/jobs/view/ URL' already in the schema, so the baseline 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 gives a specific verb and resource ('List the hiring team for a LinkedIn job'), which is clearly distinct in subject matter from siblings like linkedin_live_job_get_v2 or linkedin_live_job_similar_v2. It does not, however, explicitly contrast itself with those siblings.

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 call this versus the relatedViews, similar, or get job tools, nor any prerequisite or exclusion stated. The only constraint mentioned ('Requires jobId') is already enforced by the required array in the schema.

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