Skip to main content
Glama
kula-ai

@kula-ai/mcp-server

Official
by kula-ai

update_requisition

Updates an existing requisition. Changes are applied to specified fields; omitted custom fields are cleared. Cannot modify requisitions with closed, archived, or filled statuses.

Instructions

Update an existing requisition. Cannot modify requisitions with closed, archived, or filled statuses. Pass all custom field values in additional_info — omitted fields will be cleared.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesRequisition ID
role_nameNoJob role name for this requisition
employment_typeNoEmployment type (full_time, part_time, contract, internship, temporary, seasonal)
requisition_typeNoRequisition type (new_hire, contract, backfill, internship, internal)
department_idNoDepartment ID
office_idsNoComma-separated office IDs (at least one required)
descriptionNoRequisition description
minimum_salaryNoMinimum salary amount
maximum_salaryNoMaximum salary amount
salary_currency_idNoCurrency country ID for salary
recruiter_idNoUser ID of the assigned recruiter
hiring_manager_idNoUser ID of the hiring manager
target_hire_dateNoTarget hire date (YYYY-MM-DD)
target_start_dateNoTarget start date (YYYY-MM-DD, must be on or after target_hire_date)
confidentialNoWhether this requisition is confidential
job_idNoAssociate a job or change the associated job. Set to null to remove association.
additional_infoNoCustom field values as key-value pairs. Pass all values — omitted fields will be cleared.
apply_to_groupNoWhen true, updates all requisitions in the group. Defaults to false (requisition leaves the group).
reapproval_noteNoNote included if approval workflows trigger reapproval
Behavior4/5

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

With no annotations, the description discloses important behaviors: that it cannot modify certain statuses and that omitted custom fields in additional_info are cleared. This adds value 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with purpose, then constraints, then usage note. No wasted words, highly efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers purpose and key constraints but omits response behavior, potential side effects (e.g., reapproval workflow), and lacks guidance on using with sibling tools. Adequate but not fully comprehensive.

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 coverage is 100%, providing full parameter descriptions. The description adds clarity for additional_info (clearing behavior), but this is a single parameter enhancement, meeting the baseline.

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 clearly states the tool updates an existing requisition, distinguishing it from create_requisition and close_requisition. It also specifies constraints on statuses, adding precision.

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?

The description indicates when not to use the tool (for closed, archived, or filled statuses) and gives a key usage note about additional_info. However, it does not explicitly mention alternative tools for different statuses.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kula-ai/kula-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server