Skip to main content
Glama

get_job_details

Read-onlyIdempotent

Retrieve full public LinkedIn job details—including description, salary, skills, and applicant count—from a job ID or direct URL.

Instructions

Get full public LinkedIn job details including full description, salary, skills, and applicant count.

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": {
      "id": "<id>"
    },
    "name": "get_job_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesLinkedIn numerical job ID (e.g. '4481120122') or direct job URL

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.8
    • addedInput schema / properties / id / description
      Added value: +"LinkedIn numerical job ID (e.g. '4481120122') or direct job URL"
  2. First observedv0.1.2

TDQS

A3.6/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 the safety profile is covered. The description adds one useful qualifier, 'public', signaling that only publicly visible listing data is returned rather than recruiter- or account-scoped data. It says nothing about behavior for expired/removed postings, rate limits, or partial results.

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

Conciseness5/5

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

One sentence with the verb and resource front-loaded and the returned fields listed inline; there is no filler or redundant restatement of the name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 shape need not be explained, and the sole required parameter is fully documented in the schema. The remaining gap is workflow context — how to obtain an ID and how this differs from the many sibling job tools — which the description leaves implicit.

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% and the single 'id' parameter already documents that it accepts a numeric LinkedIn job ID or a direct job URL. The description adds no syntax, format, or validation meaning beyond that, 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?

Uses a specific verb ('Get') plus resource ('public LinkedIn job details') and enumerates what is returned: full description, salary, skills, applicant count. That lets an agent distinguish it from siblings like get_job_salary or search_jobs, though it doesn't explicitly name those alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: it retrieves full details for a known job ID, so an agent can infer it should follow a search step. There is no explicit when-to-use/when-not statement, no mention of what to do if the job ID is unknown, and no routing to sibling tools such as search_jobs or compare_jobs.

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