Skip to main content
Glama
kula-ai

@kula-ai/mcp-server

Official
by kula-ai

list_requisitions

Retrieve a paginated list of job requisitions filtered by status, department, employment type, dates, and more, respecting user permissions.

Instructions

List all requisitions for your account, respecting permissions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number
limitNoItems per page
statusNoComma-separated statuses to filter by (draft, pending_approval, approved, rejected, created, open, filled, closed, archived)
department_idsNoComma-separated department IDs to filter by
employment_typeNoComma-separated employment types to filter by (full_time, part_time, contract, internship, temporary, seasonal)
requisition_typeNoComma-separated requisition types to filter by (new_hire, contract, backfill, internship, internal)
recruiter_idsNoComma-separated recruiter user IDs to filter by
hiring_manager_idsNoComma-separated hiring manager user IDs to filter by
office_idsNoComma-separated office IDs to filter by
job_idsNoComma-separated job IDs to filter by
created_by_idsNoComma-separated user IDs to filter by creator
queryNoFull-text search query
sort_byNoField to sort by (default: created_at)
sort_orderNoSort direction
created_afterNoFilter by created date (ISO 8601, inclusive lower bound)
created_beforeNoFilter by created date (ISO 8601, inclusive upper bound)
updated_afterNoFilter by updated date (ISO 8601, inclusive lower bound)
updated_beforeNoFilter by updated date (ISO 8601, inclusive upper bound)
target_hire_date_afterNoFilter by target hire date lower bound (YYYY-MM-DD)
target_hire_date_beforeNoFilter by target hire date upper bound (YYYY-MM-DD)
target_start_date_afterNoFilter by target start date lower bound (YYYY-MM-DD)
target_start_date_beforeNoFilter by target start date upper bound (YYYY-MM-DD)
Behavior2/5

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

The description says 'respecting permissions' but does not explain what happens if permissions are insufficient. With no annotations, it fails to disclose pagination, sorting defaults, or error handling. Minimal behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is extremely concise at 7 words, stating purpose immediately. However, for a tool with 22 parameters, it could benefit from slightly more context without losing conciseness.

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

Completeness2/5

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

The description is incomplete for a complex tool. It lacks mention of return value structure, pagination behavior, or any specifics about how the many filters interact. No output schema exists to compensate.

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%, so baseline is 3. The description adds no additional meaning beyond the pre-existing parameter descriptions in the schema. It does not explain how to use filters effectively.

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?

The description clearly states the verb 'list' and resource 'requisitions', but does not distinguish from sibling tools like get_requisition or list_requisitions_fields. It implies a list operation but lacks specificity about scope and filtering.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives such as get_requisition or list_requisitions_fields. The description mentions 'for your account' but doesn't clarify how it differs from other list tools.

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