Skip to main content
Glama

SourceGeek

Get job posting

employee_job_details
Read-only

Fetch a job posting by id or jobs/view URL: title, state, description, location, employment type, job functions, industries, language, listed/expiry dates, apply URLs and the hiring company's summary.

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": {
      "jobId": "<jobId>"
    },
    "name": "employee_job_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesJob id (e.g. '4423135589') or a /jobs/view/<id> URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds value beyond that by acting as a de facto return contract, listing the fields the posting object contains even though no output schema exists. It still says nothing about rate limits, auth, or behavior on missing postings.

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, front-loaded with the verb and accepted identifier formats, followed by a tight field enumeration. Every clause carries information, and nothing is repeated or padded.

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?

For a one-parameter read tool with no output schema, the description covers both the input forms and the returned shape, which is what an agent needs to invoke it correctly. The only real omission is routing guidance versus the job-search and company-jobs siblings.

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 jobId property already documents the id-or-URL duality with an example, so the description's "by id or jobs/view URL" mostly restates it. Baseline 3 applies since the schema does the heavy lifting here.

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?

The description gives a specific verb and resource ("Fetch a job posting") and enumerates the exact payload (title, state, description, location, employment type, etc.), so an agent knows precisely what it gets back. It does not distinguish itself from siblings like employee_company_jobs or employee_search_jobs, which is the only thing keeping it from a 5.

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 takes an id or a /jobs/view URL, so the agent can infer this is the single-posting lookup. There is no explicit statement of when to choose this over employee_search_jobs or employee_company_jobs, and no note about what happens with an invalid or expired id.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources