Skip to main content
Glama
Greenhouse MCP

Greenhouse MCP

by benmonopoli

get_job_post_for_job

Fetch a specific job post scoped to a job. Returns 404 if the post doesn't belong to that job.

Instructions

Get a specific job post scoped to a job. Read-only.

Same as get_job_post, but returns 404 if the post doesn't belong to the job. To find job_id: list_jobs → match by name. To find post_id: list_job_posts_for_job.

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>",
      "job_post_id": "<job_post_id>"
    },
    "name": "get_job_post_for_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesGreenhouse job ID
job_post_idYesJob post ID

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.0
    • addedInput schema / properties / job_id / description
      Added value: +"Greenhouse job ID"
    • addedInput schema / properties / job_post_id / description
      Added value: +"Job post ID"
  2. Addedv0.3.4

TDQS

A4.7/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it delivers meaningfully: it declares 'Read-only' and specifies the 404 behavior when the post does not belong to the job. It omits auth/permission requirements and rate-limit behavior, which are the remaining gaps for a no-annotation tool.

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?

Three short sentences, front-loaded with the core purpose and the differentiating 404 behavior, then prerequisite lookups. Every sentence earns its place with no filler.

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 an output schema present, the description needn't explain return values, and it covers what matters: scope, read-only nature, error semantics, and ID discovery. An agent has everything needed to call it 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 coverage is 100%, so the baseline is 3; the description goes beyond the schema by explaining how to obtain each required ID (list_jobs → match by name; list_job_posts_for_job), which is genuine operational value not present in the field descriptions.

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 (get) and resource (job post) with an explicit scope qualifier ('scoped to a job'). It directly names and contrasts with the sibling get_job_post, so the agent can select between them without opening either schema.

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

Usage Guidelines5/5

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

Explicitly says to use get_job_post for the general case and this tool when the post must belong to the job (404 otherwise). It also provides prerequisite routing for both required IDs (list_jobs, list_job_posts_for_job), leaving nothing to inference.

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

Deploy Server

Other Tools