Skip to main content
Glama
Sign In
Greenhouse MCP

Greenhouse MCP

by benmonopoli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_user_roles

Retrieve all user roles to resolve role names to IDs for granting job permissions. Only job_admin roles can be assigned to jobs.

Instructions

List all user roles in the organization. Read-only.

Resolves role names to IDs for add_job_permission and add_future_job_permission. Only roles with role_type 'job_admin' can be granted on jobs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_user_roles"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoPass next_cursor from the previous response to get the next page
per_pageNoResults per page (max 500)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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"
+}
    • 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.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does declare 'Read-only' explicitly, plus the domain constraint that only role_type 'job_admin' roles can be granted on jobs. It omits permission/auth requirements and pagination behavior, but pagination is covered by the schema and an output schema exists for return values.

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?

Four short sentences, front-loaded with purpose, followed by safety, use case, and constraint. Nothing is redundant and each sentence adds information.

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?

Purpose, read-only nature, intended downstream use, and the role_type constraint are all present; parameters are fully covered by the schema and an output schema handles return values. An agent has everything needed to call this correctly.

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 cursor and per_page are fully documented in the schema and the description adds no syntax or format detail beyond that. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('List all user roles in the organization') and scopes it clearly enough to separate it from sibling list tools such as list_users, list_job_permissions, and list_future_job_permissions.

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 names the downstream consumers of this data ('Resolves role names to IDs for add_job_permission and add_future_job_permission'), which tells the agent why and when to call it. It stops short of stating exclusions (e.g. when to use list_job_permissions instead), so it is clear context without full when-not guidance.

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