Skip to main content
Glama
Sign In
Greenhouse MCP

Greenhouse MCP

by benmonopoli
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

remove_education

Delete a candidate's education entry after verifying it belongs to that candidate. Use candidate_id and education_id from the profile.

Instructions

Remove an education entry from a candidate. Write operation.

To find candidate_id: search_candidates_by_name. For education_id: get_candidate → check the educations array. Checks the record belongs to this candidate before deleting it.

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": {
      "candidate_id": "<candidate_id>",
      "education_id": "<education_id>"
    },
    "name": "remove_education"
  }
}

Input Schema

NameRequiredDescriptionDefault
candidate_idYesGreenhouse candidate ID
education_idYesEducation record ID from the candidate's profile

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.0
    • addedInput schema / properties / candidate_id / description
      Added value: +"Greenhouse candidate ID"
    • addedInput schema / properties / education_id / description
      Added value: +"Education record ID from the candidate's profile"
  2. Addedv0.3.4

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose two meaningful traits: that this is a write (destructive) operation and that it validates record ownership before deleting. It still omits irreversibility, failure behavior, and required permissions, so it is strong but not exhaustive.

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 the action and its nature, followed by lookup instructions and the safety check. No filler and nothing repeated from the schema.

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 described, and the description covers the mutation's nature, ID discovery, and ownership validation. Given zero annotations and a destructive operation, it could say more about irreversibility or error cases, but it is close to sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds real value by explaining how each required ID is obtained (search_candidates_by_name for candidate_id, get_candidate's educations array for education_id) — provenance the schema itself does not convey.

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 ('Remove an education entry from a candidate') and identifies it as a write operation. It is clearly distinguishable from sibling tools like add_education, remove_employment, and delete_candidate without opening any schema.

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?

Provides concrete routing guidance: use search_candidates_by_name for candidate_id and get_candidate to read the educations array for education_id. It does not, however, state when this tool should be preferred over alternatives or any exclusions, so it stops short of full when/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