Skip to main content
Glama
Sign In
Greenhouse MCP

Greenhouse MCP

by benmonopoli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_offer

Retrieve a single offer by ID to check status, version, key dates, opening ID, and custom fields. Use this read-only lookup when you have an offer ID from a list.

Instructions

Get a single offer by ID. Read-only.

Returns offer status, version, starts_on, sent_on, resolved_at, opening_id, and custom fields.

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": {
      "offer_id": "<offer_id>"
    },
    "name": "get_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
offer_idYesOffer ID — get from list_offers or list_offers_for_application

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • addedInput schema / properties / offer_id / description
      Added value: +"Offer ID — get from list_offers or list_offers_for_application"
  2. Addedv0.3.4

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden and does disclose 'Read-only', which is a useful safety trait. However, it says nothing about permission requirements, behavior when the ID does not exist, or rate limits, and the listed return fields duplicate what the output schema already provides.

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?

Two short sentences, front-loaded with the core action and scoping, followed by the safety note and return summary. No filler or redundancy.

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?

For a simple single-record lookup with a 100%-covered schema and an output schema, the description is largely sufficient, and it usefully adds the read-only guarantee that missing annotations would otherwise leave unstated. Minor gaps around not-found/error behavior keep it from a 5.

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 description coverage is 100% and the single parameter is fully documented in the schema, including where to source the ID. The description adds no syntax or format detail beyond 'by ID', so the baseline 3 applies.

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 ('Get a single offer by ID') and scopes it to one record, which distinguishes it from plural siblings like list_offers and the differently-scoped get_current_offer. An agent can identify the tool without opening its schema.

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

Usage Guidelines2/5

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

The description gives no explicit when-to-use guidance, no when-not conditions, and does not name alternatives such as list_offers or get_current_offer. The only routing hint (fetch the ID from list_offers) lives in the schema's parameter description, not the tool description.

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