Skip to main content
Glama
Sign In
Greenhouse MCP

Greenhouse MCP

by benmonopoli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_rejection_reasons

Retrieve rejection reason names and IDs to pass the correct ID to reject_application or bulk_reject. Use it to map user phrases like 'not enough experience' before rejecting.

Instructions

List all rejection reasons. Read-only.

Resolves rejection reason names to IDs. When a user says "reject for 'not enough experience'," use this to find the ID, then pass it to reject_application or bulk_reject. Each reason's type is an object {id, key, name} — key is WE_REJECTED_THEM, THEY_REJECTED_US, NONE_SPECIFIED or SECURITY_CONCERN.

Input Schema

NameRequiredDescriptionDefault
cursorNoPass next_cursor from the previous response to get the next page
per_pageNoResults per page (max 500)
force_refreshNoBypass cache and fetch fresh data
include_defaultsNoAlso include Greenhouse's built-in default reasons

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.5.0
    • 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 / force_refresh / description
      Added value: +"Bypass cache and fetch fresh data"
    • addedInput schema / properties / include_defaults
      Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Also include Greenhouse's built-in default reasons",
+  "title": "Include Defaults"
+}
    • removedInput schema / properties / page
      Removed value: -{
-  "default": 1,
-  "title": "Page",
-  "type": "integer"
-}
    • addedInput schema / properties / per_page / description
      Added value: +"Results per page (max 500)"
  2. Addedv0.3.4

TDQS

A4.1/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 burden and it does declare 'Read-only' plus explains the shape and enum keys of each reason's `type` object (WE_REJECTED_THEM, THEY_REJECTED_US, NONE_SPECIFIED, SECURITY_CONCERN). It does not mention pagination behavior or auth requirements, but the enum-key disclosure is genuine added context beyond the schema.

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-loaded with purpose and read-only status in the first line, then the workflow, then the type-object detail. Slightly padded by the return-shape explanation, but every sentence is relevant and there is no filler.

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?

An output schema exists, so return values need not be re-explained, and the description covers purpose, safety profile and the downstream consumption pattern. Minor gaps remain around pagination and the default/refresh flags, but nothing an agent needs to invoke it correctly is missing.

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% — cursor, per_page, force_refresh and include_defaults are all documented in the schema itself. The description adds no parameter-level guidance (e.g. when to set include_defaults or force_refresh), so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List all rejection reasons') and adds the actual purpose — resolving reason names to IDs. It does not explicitly distinguish itself from the sibling list_close_reasons, so it stops short of a 5, but the resource is specific enough that an agent can tell it apart from the surrounding list_* tools.

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 describes the triggering situation ('When a user says "reject for not enough experience"') and the follow-on action ('use this to find the ID, then pass it to reject_application or bulk_reject'). It names the concrete alternatives that consume the output, 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