Skip to main content
Glama
Sign In
Greenhouse MCP

Greenhouse MCP

by benmonopoli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_questions_for_question_set

List all questions in a demographic question set by ID. Use list_question_sets to find the question_set_id first.

Instructions

List questions in a specific demographic question set. Read-only.

To find question_set_id: list_question_sets.

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": {
      "question_set_id": "<question_set_id>"
    },
    "name": "list_questions_for_question_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
question_set_idYesQuestion set ID — get from list_question_sets

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • addedInput schema / properties / question_set_id / description
      Added value: +"Question set ID — get from list_question_sets"
  2. Addedv0.3.4

TDQS

A3.6/5.0
Behavior3/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; it does disclose 'Read-only,' which is the essential safety trait for a retrieval tool. It says nothing about pagination, ordering, or what happens with an invalid/empty question set, but the presence of an output schema lowers the bar for return-value disclosure.

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 lines with zero filler; the purpose is front-loaded and the ID-sourcing hint follows immediately. Every sentence earns its place.

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 single-parameter read-only list with an output schema, the description covers the scope and how to source the required ID, which is enough to call it correctly. A brief note on ordering or page size would close the remaining gap but is not essential.

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 already documents 'Question set ID — get from list_question_sets', so the description's identical hint adds nothing new. Baseline 3 applies 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.

Purpose4/5

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

States a specific verb (List) and resource (questions) scoped to a demographic question set, which distinguishes it from the sibling list_questions that presumably lists all questions. However, it never names that sibling or any other alternative explicitly.

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

Usage Guidelines3/5

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

Gives actionable guidance on obtaining the required question_set_id via list_question_sets, which is genuine usage help. It stops short of stating when to prefer this over list_questions or any related retrieval tool, leaving the scoping choice 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