Fresh Linkedin Profile Data MCP Server

Search Jobs V2

search_jobs_v2

Search LinkedIn for job listings using a simplified request payload. Retrieve job results from LinkedIn profile data with one API call.

Instructions

Using a simpler payload. 1 credit per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_jobs_v2"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Sep 4, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description must carry behavioral disclosure, and it only reveals credit cost. It does not mention response behavior, result limits, side effects, or error/timeout behavior, which an unannotated tool needs.

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?

Two short sentences with no filler; the credit cost is useful operational information and is front-loaded after the payload note. It is concise, though this brevity contributes to incompleteness elsewhere.

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?

For an unannotated, schema-less search tool, the description is incomplete: it does not state what job search parameters or filters are available, what the results look like, or when this variant should be used. Cost alone is not enough context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has zero parameters and 100% coverage, so the baseline is 4: there are no parameter meanings to explain. The description's mention of a simpler payload is consistent but adds no parameter-level detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description never explicitly states what the tool does; it only adds 'Using a simpler payload,' which presumes the purpose is already known from the name. It offers a comparative distinction from a sibling like search_jobs but no specific verb-resource statement.

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 about when to call search_jobs_v2 versus search_jobs or related search tools. 'Simpler payload' implies a reason to prefer it, but no condition or exclusion is stated.

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

Deploy Server