LinkedIn MCP Zero

by SanthaKumar-K-2004

Overview Schema Source Related Servers Discussions Admin

analyze_job_viability

Read-onlyIdempotent

Assess hiring viability, applicant saturation, and ghost-job probability for a LinkedIn job using public signals and a job ID or URL.

Instructions

Assess hiring viability, applicant saturation, and ghost-job probability based on public signals.

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": {
      "job_id_or_url": "<job_id_or_url>"
    },
    "name": "analyze_job_viability"
  }
}

Input Schema

Name	Required	Description	Default
`job_id_or_url`	Yes	LinkedIn numerical job ID (e.g. '4481120122') or direct job URL

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.4.8Nov 4, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety behavior is covered. The phrase 'based on public signals' usefully hints that outputs are heuristic estimates rather than verified facts, but the description doesn't state confidence limits, data recency, or what happens with invalid/expired job IDs.

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?

A single well-formed sentence with the three analytical outputs front-loaded and zero filler. It is possibly too terse for a multi-faceted analysis tool, but nothing in it is wasted.

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?

An output schema exists, so return values need no explanation, and the input is fully specified. However, for an analysis tool that produces probabilistic judgments, the description omits what signals feed the assessment and any caveats, leaving the agent without enough to interpret results confidently.

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?

With a single parameter at 100% schema coverage, the schema already documents the accepted LinkedIn numeric ID or direct URL formats with an example. The description adds no additional meaning about the input, 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?

Names a specific verb+resource set: hiring viability, applicant saturation, and ghost-job probability for a given job posting. An agent can distinguish it from search_jobs or get_job_details, though it never explicitly names which sibling to prefer.

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 explicit when-to-use or when-not-to-use guidance and no named alternative. Usage is only implied — an agent must infer that this is the evaluation step after finding a job posting, and must guess whether it supersedes or complements get_job_details or get_job_trends.

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