Skip to main content
Glama

Get a job posting

get_job
Read-onlyIdempotent

The full posting behind one search_jobs result: description, pay, locations, seniority and its Aworkado link, where the candidate applies.

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": "get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesThe id of a search_jobs result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the content scope (description, pay, locations, seniority, Aworkado link, application destination) but says nothing about failure modes for a bad id, rate limits, or freshness of 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 scope ('the full posting behind one search_jobs result') and then the returned fields. No filler and nothing redundant with the title.

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?

With no output schema, the description carries the burden of describing returns and does so by enumerating the key fields including the application destination. It is nearly complete for a simple one-parameter getter, missing only error or availability behavior.

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% and the single jobId parameter is already documented as 'the id of a search_jobs result'. The description reinforces the origin of that id (one search_jobs result), which slightly strengthens the semantic link between the two tools beyond the schema alone.

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?

Names a specific verb (retrieve the full posting) and resource (one job posting), scoped explicitly to 'behind one search_jobs result', which distinguishes it from the sibling search_jobs tool without needing the 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?

The phrase 'behind one search_jobs result' makes the usage path clear: call search_jobs first, then fetch a single posting. It stops short of stating exclusions or what to do when no jobId is available, so it is clear context rather than explicit when/when-not guidance.

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.