Skip to main content
Glama

Server Details

Ask Greenhouse the messy recruiting-ops questions dashboards miss by connecting candidates, applications, jobs, openings, stages, scorecards, interviews, notes, sources, referrers, offers, users, departments, and rejection details. Find referral SLA misses, feedback debt by interviewer and hiring team, stage-age outliers by owner, funnel leakage by recruiter/source/function, opening fill-risk from headcount vs active pipeline, offer-draft hygiene gaps, rejection-reason drift, and the bottleneck

Ownership verified

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Last Tested
Transport
Streamable HTTP
URL

TDQS

B3.2/5.0

Scored across 88 tools

Disambiguation4/5

Tools are mostly distinct with clear descriptions. Some overlap exists (e.g., list_job_owners vs. remove_job_coordinator_owner), but each targets a specific resource or aspect. The separation of patch_offer_* tools into compensation, core, and custom fields is slightly overlapping but still distinguishable by field subset.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (add_, get_, list_, patch_, reject_, update_, upsert_). No mixing of styles or vague verbs. The pattern is predictable and aids navigation.

Tool Count2/5

88 tools is excessively large for a single MCP server. While the domain (Greenhouse recruiting ops) is broad, this many tools likely overwhelms model selection and introduces redundancy. Calibration suggests 25+ tools is too heavy, and this far exceeds that.

Completeness4/5

The tool set covers a comprehensive range of recruiting operations, including candidates, applications, jobs, offers, interviews, scorecards, approvals, users, and permissions. Gaps exist (e.g., no submit-offer approval, no candidate delete), but the surface is quite complete for common workflows and creates no dead ends for most use cases.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Addedcreate_standing_query
  2. 87 tool updates
    • First observedadd_job_coordinator_owner
    • First observedadd_job_recruiter_owner
    • First observedcreate_offer_draft
    • First observeddeprecate_offer_draft
    • First observedget_application
    • First observedget_candidate
    • First observedget_control_plane_capabilities
    • First observedget_job
    • First observedget_offer_letter_context
    • First observedget_user
    • First observedlist_application_stages
    • First observedlist_applications
    • First observedlist_applied_candidate_tags
    • First observedlist_approval_flows
    • First observedlist_approver_groups
    • First observedlist_approvers
    • First observedlist_blocked_spam_sources
    • First observedlist_bulk_requests
    • First observedlist_candidate_attribute_types
    • First observedlist_candidate_educations
    • First observedlist_candidate_employments
    • First observedlist_candidate_tags
    • First observedlist_candidates
    • First observedlist_close_reasons
    • First observedlist_custom_field_departments
    • First observedlist_custom_field_offices
    • First observedlist_custom_field_options
    • First observedlist_custom_fields
    • First observedlist_default_interviewers
    • First observedlist_departments
    • First observedlist_email_templates
    • First observedlist_focus_candidate_attributes
    • First observedlist_future_job_permissions
    • First observedlist_interview_kits
    • First observedlist_interviewer_tags
    • First observedlist_interviewers
    • First observedlist_interviews
    • First observedlist_job_board_custom_locations
    • First observedlist_job_candidate_attributes
    • First observedlist_job_hiring_managers
    • First observedlist_job_interview_stages
    • First observedlist_job_interviews
    • First observedlist_job_notes
    • First observedlist_job_owners
    • First observedlist_job_post_locations
    • First observedlist_job_posts
    • First observedlist_jobs
    • First observedlist_notes
    • First observedlist_offers
    • First observedlist_offices
    • First observedlist_openings
    • First observedlist_prospect_details
    • First observedlist_prospect_pool_stages
    • First observedlist_prospect_pools
    • First observedlist_referrers
    • First observedlist_rejection_details
    • First observedlist_rejection_reasons
    • First observedlist_scheduled_interviews
    • First observedlist_scorecard_candidate_attributes
    • First observedlist_scorecard_question_answer_options
    • First observedlist_scorecard_question_answers
    • First observedlist_scorecard_question_candidate_attributes
    • First observedlist_scorecard_question_options
    • First observedlist_scorecard_questions
    • First observedlist_scorecards
    • First observedlist_sources
    • First observedlist_tracking_links
    • First observedlist_user_emails
    • First observedlist_user_job_permissions
    • First observedlist_user_roles
    • First observedlist_users
    • First observedmove_application_to_stage
    • First observedpatch_application_metadata
    • First observedpatch_candidate_contact
    • First observedpatch_candidate_custom_fields
    • First observedpatch_candidate_profile
    • First observedpatch_offer_compensation
    • First observedpatch_offer_core
    • First observedpatch_offer_custom_fields
    • First observedpatch_opening_metadata
    • First observedreject_application
    • First observedremove_job_coordinator_owner
    • First observedremove_job_recruiter_owner
    • First observedupdate_application_assignment
    • First observedupsert_application_note
    • First observedupsert_job_note
    • First observedupsert_offer_review_note

Related MCP Servers

  • A
    license
    A
    quality
    C
    maintenance
    Enables brand visibility monitoring across major AI platforms like ChatGPT, Claude, Gemini, and Perplexity. It allows users to track visibility scores, analyze competitor data, and receive actionable insights to improve AI-generated brand recommendations.
    16
    9 npm
    1
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables tracking competitor websites, changelogs, blog feeds, and pricing pages with meaningful diffs, classification, and Markdown digests via MCP tools for listing, adding, removing competitors, running checks, and retrieving digests or changes.
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Browse IndustryLens's published competitive-intelligence reports and head-to-head competitor comparisons from any AI agent — real, source-backed data.
    MIT
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources