JobCrawls

Get full job listing details

get_job_details

Read-onlyIdempotent

Returns the complete details of one JobCrawls listing by its id (the id field of a search_jobs result): full description, requirements, responsibilities, benefits, salary, company, location, application deadline and a direct link to the posting. Listings sourced from Job Market Finland (Työmarkkinatori) have isTyomarkkinatori: true and include a dataSource attribution required by Job Market Finland's terms of use. Reuse: figures may be quoted with a visible link to the jobcrawls.com page in the result (or "JobCrawls (jobcrawls.com)" where a link is impossible); each result repeats this in dataUse.

Input Schema

Name	Required	Description	Default
`jobId`	Yes	The listing id (the `id` field returned by search_jobs). Required.
`locale`	No	Language of the user's message (fi for Finnish, sv for Swedish, en for English or any other language), including when job titles or place names in it are English. Language to return the listing content in: en = English, fi = Finnish, sv = Swedish, normally the locale of the search the id came from. This call has no query text to detect language from, so it defaults to en when omitted. If the listing is not available in that language the connector falls back to whichever language it exists in.

Output Schema

Name	Required	Description
`id`	Yes
`url`	Yes	Direct link to the individual posting on jobcrawls.com (or the source posting).
`field`	Yes
`title`	Yes
`locale`	Yes	Language index the listing was found in.
`salary`	Yes	Advertised salary range, or null when the listing states none.
`skills`	Yes
`company`	Yes
`jobType`	Yes
`logoUrl`	Yes
`benefits`	Yes
`isActive`	Yes
`location`	Yes	One location, or several for multi-location listings.
`roleLevel`	Yes
`brandColor`	Yes
`companyUrl`	Yes
`dataSource`	No	Present only when isTyomarkkinatori is true. Attribution required alongside the listing by Job Market Finland's terms of use.
`postedDate`	Yes	YYYY-MM-DD.
`remoteness`	Yes
`description`	Yes
`marketSalary`	Yes	What the role pays in the market (gross EUR per month, the JobCrawls salary pages figures), only next to an employer-stated salary; null otherwise.
`requirements`	Yes
`employerGrade`	Yes	JobCrawls Employer Score as a letter grade (A best), or null when the employer is not scored.
`educationLevel`	Yes
`responsibilities`	Yes
`salaryIsEstimate`	Yes	True when `salary` is a JobCrawls market-based estimate rather than stated by the employer.
`isTyomarkkinatori`	Yes	True when the listing is sourced from Job Market Finland (Työmarkkinatori).
`languagesRequired`	Yes
`applicationDeadline`	Yes	YYYY-MM-DD, or null when none is stated.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 21, 2026

changedOutput schema / properties / marketSalary / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {
-      "currency": {
-        "type": "string"
-      },
-      "median": {
-        "type": "number"
-      },
-      "p25": {
-        "type": "number"
-      },
-      "p75": {
-        "type": "number"
-      },
-      "period": {
-        "type": "string"
-      },
-      "sampleSize": {
-        "description": "Number of comparable postings the band is based on.",
-        "type": "number"
-      }
-    },
-    "required": [
-      "p25",
-      "median",
-      "p75",
-      "sampleSize",
-      "currency",
-      "period"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "currency": {
+        "type": "string"
+      },
+      "median": {
+        "type": "number"
+      },
+      "p25": {
+        "type": "number"
+      },
+      "p75": {
+        "type": "number"
+      },
+      "period": {
+        "type": "string"
+      },
+      "sampleSize": {
+        "description": "Number of comparable postings the band is based on (with source statistics_finland: the ads behind the place and level differences).",
+        "type": "number"
+      },
+      "source": {
+        "description": "statistics_finland: Statistics Finland earnings for the occupation raised to today, moved by job-ad differences (the JobCrawls salary pages figures). job_ads: stated pay in job ads.",
+        "enum": [
+          "statistics_finland",
+          "job_ads"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "p25",
+      "median",
+      "p75",
+      "sampleSize",
+      "currency",
+      "period"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / marketSalary / description

Previous value: -"Market salary band (gross EUR per month) for comparable jobs, only next to an employer-stated salary; null otherwise."New value: +"What the role pays in the market (gross EUR per month, the JobCrawls salary pages figures), only next to an employer-stated salary; null otherwise."

Changed3 schema fields changedOct 18, 2026

changedInput schema / properties / locale / description

Previous value: -"Set this to the language of the user's message (fi for Finnish, sv for Swedish, en for English or any other language), even when the job titles or place names in it are English. Language to return the listing content in: en = English, fi = Finnish, sv = Swedish. Pass the same locale you searched in; this call has no query text to detect language from, so it defaults to en when omitted. If the listing is not available in that language the connector falls back to whichever language it exists in."New value: +"Language of the user's message (fi for Finnish, sv for Swedish, en for English or any other language), including when job titles or place names in it are English. Language to return the listing content in: en = English, fi = Finnish, sv = Swedish, normally the locale of the search the id came from. This call has no query text to detect language from, so it defaults to en when omitted. If the listing is not available in that language the connector falls back to whichever language it exists in."

changedOutput schema / properties / dataSource / description

Previous value: -"Present only when isTyomarkkinatori is true. Attribution that MUST be shown alongside the listing, per Job Market Finland's terms of use."New value: +"Present only when isTyomarkkinatori is true. Attribution required alongside the listing by Job Market Finland's terms of use."

changedOutput schema / properties / salaryIsEstimate / description

Previous value: -"True when `salary` is a JobCrawls market-based estimate rather than stated by the employer. Say so when presenting it."New value: +"True when `salary` is a JobCrawls market-based estimate rather than stated by the employer."

First observedOct 5, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds genuinely non-structured behavior: Job Market Finland data carries isTyomarkkinatori plus a mandatory dataSource attribution, results repeat reuse terms in dataUse, and locale falls back to another language when the listing is unavailable. It does not mention error behavior for a bad/expired id, which is the remaining gap.

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?

Purpose and id source are front-loaded in the first clause, and the licensing/attribution sentences earn their place because they impose an obligation on the agent. The enumerated field list (description, requirements, responsibilities, benefits, salary, ...) partially duplicates the output schema, which is the only real padding.

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 values need not be explained, and the description nonetheless covers the two things structured data cannot convey: the source of the required id and the attribution/reuse obligations attached to the results. Only edge-case behavior (invalid id, listing removed) is absent, which is minor for a read-only lookup.

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 both parameters are fully documented in the schema, so the baseline is 3. The description only restates that jobId is a search_jobs `id` and echoes the locale fallback rule already present in the schema; it adds no format or constraint detail beyond that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a precise verb+resource ('Returns the complete details of one JobCrawls listing by its id') and immediately disambiguates from the sibling search_jobs by stating the id comes from that tool's results. An agent can distinguish this detail-fetch tool from calculate_net_salary_finland, list_job_filters and search_jobs without opening any schema.

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

Usage Guidelines4/5

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

States the precondition for calling it (you need an id, which is 'the `id` field of a search_jobs result'), which effectively routes the agent through search_jobs first, and the locale guidance ('normally the locale of the search the id came from') tells the agent how to fill the optional argument. It stops short of an explicit when-not/exclusion statement, but the context is unambiguous.

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

All JobCrawls tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?