Skip to main content
Glama

Read a published opening

get_job
Read-onlyIdempotent

Read one current published opening in full, with its company profile, the company's application URL, its rolefig page and, when the company gave them, teamAnswers: a named person on the hiring team answering why the role exists, its hardest part and a normal week, in their own words, each answer with an audioUrl when they published their recording. Use the company and job slugs from search_jobs. Compensation text is authoritative; absent numeric pay and units are unknown. Never submits an application.

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

Input Schema

NameRequiredDescriptionDefault
jobYes
companyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it describes the returned content in detail: company profile, application URL, rolefig page, and optional teamAnswers with audioUrl. It also adds important caveats that compensation text is authoritative, absent numeric pay and units are unknown, and the tool never submits an application.

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?

The description is front-loaded with the core action and then explains return details and caveats. It is appropriately sized for the richness it conveys, though the middle section is dense and would be easier to scan if split into shorter sentences.

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?

There is no output schema, but the description explains the returned payload including optional teamAnswers and audioUrl, and it clarifies compensation interpretation. Combined with the read-only annotations, this is complete enough for an agent to select and invoke the tool correctly.

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 description coverage is 0%, so the description must carry parameter meaning. It identifies both inputs as slugs and says to use company and job slugs from search_jobs, compensating well for the missing schema descriptions, though it does not add examples or edge-case formatting guidance beyond the schema pattern.

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?

The description states a specific verb and resource: reading one current published opening in full. It also names the scope and the relationship to search_jobs for obtaining the required slugs, which distinguishes this from broad search tools.

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?

It clearly tells the agent to use company and job slugs from search_jobs, giving a concrete usage path. It does not explicitly exclude or compare against nearby siblings such as demo_get_job or check_job_posting, so it stops short of full 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.

Resources