get_jobs_detail_jobId — linkedin MCP Tool Read-only
get_jobs_detail_jobId
(get jobs detail job id) is one of 12 tools on the
linkedin
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_jobs_detail_jobId from your client
- Claude Code linkedin get_jobs_detail_jobId run in your project directory
- Claude Desktop linkedin get_jobs_detail_jobId ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor linkedin get_jobs_detail_jobId ~/.cursor/mcp.json
- VS Code linkedin get_jobs_detail_jobId .vscode/mcp.json
- Zed linkedin get_jobs_detail_jobId ~/.config/zed/settings.json
- Windsurf linkedin get_jobs_detail_jobId ~/.codeium/windsurf/mcp_config.json
- Cline linkedin get_jobs_detail_jobId ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI linkedin get_jobs_detail_jobId ~/.gemini/settings.json
- Grok linkedin get_jobs_detail_jobId .mcp.json (in your project root)
- ChatGPT linkedin get_jobs_detail_jobId Settings → Connectors → Advanced → Developer mode
- Claude.ai linkedin get_jobs_detail_jobId Settings → Connectors → Add custom connector
- LangChain linkedin get_jobs_detail_jobId pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http linkedin https://mcp.jojapi.com/linkedinOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.