LinkedIn MCP Zero

by SanthaKumar-K-2004

Overview Schema Source Related Servers Discussions Admin

deep_industry_analysis

Read-onlyIdempotent

Analyze an industry vertical by scanning active job postings and tracking real-time progress to understand hiring demand.

Instructions

Full industry analysis with real-time progress updates across active job postings.

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": {
      "industry": "<industry>"
    },
    "name": "deep_industry_analysis"
  }
}

Input Schema

Name	Required	Description	Default
`industry`	Yes	Industry vertical name (e.g. 'Artificial Intelligence', 'Fintech', 'Semiconductors')

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.4.8Nov 4, 2026

TDQS

C2.7/5.0

Behavior3/5

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

Annotations already cover read-only, idempotent, non-destructive, and open-world behavior, so the safety profile is handled. The description does add one genuinely new trait — 'real-time progress updates' — implying a long-running operation with streaming progress, but it leaves latency, duration, and whether the call blocks or streams entirely unstated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with no wasted words and the core scope front-loaded. However, the brevity reads as under-specification for a tool advertised as a 'full' analysis, so it is not efficient so much as thin.

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?

An output schema exists, so return values need not be explained, but this is a complex, long-running analysis tool and the description never clarifies what the analysis covers, how progress updates are delivered, or how it relates to the many sibling analysis tools. The one behavioral hook it introduces ('real-time progress updates') is left unexplained.

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 coverage is 100% and the single 'industry' parameter is documented with concrete examples, so the baseline is 3. The description adds nothing about the parameter beyond what the schema already says; 'across active job postings' scopes the analysis but not the input format.

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 names a resource ('industry analysis') and a scope ('across active job postings'), but uses a nominalized phrase rather than a clear verb, and never distinguishes it from the sibling 'get_industry_insights' or 'get_job_trends'. An agent cannot confidently tell which of these three industry-related tools to pick.

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 when-to-use guidance, no preconditions, and no named alternative despite several closely related siblings. The only implicit signal is 'full ... analysis', which hints at a heavyweight option without saying so.

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