Skip to main content
Glama

Youth4work (public, no sign-in)

Get job

get_job
Read-onlyIdempotent

Full details of one live job by id (from search_jobs): description, skills, courses, salary, experience, company page and the apply url. Government jobs (government=true) carry the notice details such as eligibility and last date; the person applies on the job page. Recruiter contact details are not shared.

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_id": "<job_id>"
    },
    "name": "get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesJob id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new context: government jobs surface notice details like eligibility and last date with the actual application happening on the job page, and recruiter contacts are deliberately withheld, which tells the agent what data will and will not be present.

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?

Two dense sentences with the core purpose front-loaded and the returned fields listed immediately after. The government-jobs clause is slightly tangential but justifies itself by explaining an output variation and where the application occurs.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With one required integer parameter, full schema coverage, no output schema and rich annotations, the description covers everything an agent needs: what it returns, where the id comes from, a special-case output shape, and a known data exclusion.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single job_id parameter, so the baseline is already high. The description contributes provenance by tying the id to search_jobs, which is meaning the schema's 'Job id' text does not supply.

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?

States a specific verb and resource ('Full details of one live job by id') and enumerates the payload fields (description, skills, courses, salary, experience, company page, apply url). It also distinguishes itself from the sibling search_jobs by noting the id originates there, so an agent can pick between listing and fetching.

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?

The parenthetical '(from search_jobs)' makes the usage path clear: call search_jobs first, then fetch a single job by the returned id. There is no explicit exclusion or statement of when not to use it, but the retrieval context is unambiguous for a single-resource getter.

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