Skip to main content
Glama
benmonopoli

Greenhouse MCP

by benmonopoli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_offers

Retrieve read-only offers across applications. Filter by job, status, or creation date, and return every revision or only current offers.

Instructions

List offers across all applications. Read-only.

Each offer has id, version, application_id, candidate_id, job_id, opening_id, status, starts_on, sent_on, resolved_at, and custom_fields. Every revision is returned (older ones have status 'Deprecated'); set current_only=true for just each application's current offer. For a specific candidate's offers, use list_offers_for_application (search_candidates_by_name → list_applications(candidate_id=...) → match the application → use its ID).

Input Schema

NameRequiredDescriptionDefault
cursorNoPass next_cursor from the previous response to get the next page
job_idNoOnly offers on this job — get ID from list_jobs
statusNoFilter by status: 'Created', 'Accepted', 'Rejected', or 'Deprecated'
paginateNo'single' for one page, 'all' to auto-fetch every pagesingle
per_pageNoResults per page (max 500)
current_onlyNotrue to return only the latest version of each application's offer
created_afterNoISO 8601 datetime — only offers created at/after this
created_beforeNoISO 8601 datetime — only offers created before this

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.5.0
    • addedInput schema / properties / created_after / description
      Added value: +"ISO 8601 datetime — only offers created at/after this"
    • addedInput schema / properties / created_before / description
      Added value: +"ISO 8601 datetime — only offers created before this"
    • addedInput schema / properties / current_only
      Added value: +{
+  "default": false,
+  "description": "true to return only the latest version of each application's offer",
+  "title": "Current Only",
+  "type": "boolean"
+}
    • addedInput schema / properties / cursor
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Pass next_cursor from the previous response to get the next page",
+  "title": "Cursor"
+}
    • addedInput schema / properties / job_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Only offers on this job — get ID from list_jobs",
+  "title": "Job Id"
+}
    • removedInput schema / properties / page
      Removed value: -{
-  "default": 1,
-  "title": "Page",
-  "type": "integer"
-}
    • addedInput schema / properties / paginate / description
      Added value: +"'single' for one page, 'all' to auto-fetch every page"
    • addedInput schema / properties / per_page / description
      Added value: +"Results per page (max 500)"
    • addedInput schema / properties / status
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Filter by status: 'Created', 'Accepted', 'Rejected', or 'Deprecated'",
+  "title": "Status"
+}
  2. Addedv0.3.4

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it does disclose the key non-obvious trait: every revision is returned and older ones carry status 'Deprecated'. It also declares read-only explicitly. It does not cover auth/permission requirements or rate limits, which keeps it short of a 5.

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?

Front-loads purpose and read-only status, then behavior, then the alternative route — a sensible order with no filler. The parenthetical call chain is slightly verbose but earns its place by preventing a wrong tool choice.

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 an output schema present, return values need no explanation, and the description still usefully previews the returned fields and revision semantics. Read-only status, filtering mode and the sibling route are all covered; only permission/auth prerequisites are absent.

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%, so the schema already documents cursor, job_id, status, paginate, per_page and date filters. The description's explanation of current_only largely restates the schema's own wording, so it adds little beyond the structured fields; baseline 3 is appropriate.

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 ('List offers across all applications') and immediately distinguishes itself from the closely-named siblings get_offer, get_current_offer and list_offers_for_application. An agent can tell what this tool returns and at what scope without opening a 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 names the alternative for a narrower case ('For a specific candidate's offers, use list_offers_for_application') and even supplies the chained call path (search_candidates_by_name -> list_applications -> match application -> use its ID). It also gives the condition for switching modes (current_only=true for just the current offer), so routing is unambiguous.

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