Djinni MCP

Overview Schema Source Related Servers Discussions Admin

get_job

Read-only

Retrieve a public Djinni vacancy by numeric ID or HTTPS job URL and inspect activity evidence, with explicit description truncation reporting and nulls for missing fields.

Instructions

Read a public vacancy by numeric ID or HTTPS Djinni job URL and inspect current activity evidence. Missing fields remain null. Source dates can be updates. Description is plain untrusted text; truncation is reported explicitly.

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": {
      "job": "<job>"
    },
    "name": "get_job"
  }
}

Input Schema

Name	Required	Description	Default
`job`	Yes
`description_limit`	No

Output Schema

Name	Required	Default
`job`	Yes
`warnings`	Yes
`checked_at`	Yes
`contract_version`	No	0.1

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Nov 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Beyond the readOnly/openWorld annotations, it discloses null handling for missing fields, that source dates may reflect updates rather than creation, that the description text is untrusted, and that truncation is reported. That is meaningful behavioral context an agent could not infer from the annotations or schema.

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?

Four short clauses, zero padding, and the core action is front-loaded ahead of the caveats. The telegraphic style is slightly clipped but never wasteful.

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 needn't be described, and the description still covers null semantics and truncation reporting. The main gap is that the description_limit parameter's purpose and bounds are never spelled out.

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 0%, so the description must carry parameter meaning. It explains the required `job` parameter as an ID-or-URL, which is genuinely useful, but `description_limit` is only hinted at through the mention of truncation and its default, range, and unit are never stated.

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 uses a specific verb and resource ("Read a public vacancy") and names the accepted locators (numeric ID or HTTPS Djinni job URL), which implicitly sets it apart from the sibling search_jobs. It stops short of explicitly contrasting itself with siblings, so 4 rather than 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?

UseWhen is only implied: you fetch by ID or URL when you already have one. There is no explicit guidance on when to use this instead of search_jobs, nor any exclusions or prerequisites.

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

Deploy Server