Skip to main content
Glama

create_recruiting_review

Create a recruiting review to initiate an interview process for a candidate, configure title and date, and optionally add description, verdict, participants, and company details.

Instructions

Create a Recruiting review/interview like the Huly UI: increments RVE sequence, attaches to the candidate reviews collection, stores markdown description as Huly markup, defaults dueDate to 30 minutes after date, and recruit-enables the person if needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
candidateYesa string that will be trimmed
titleYesa string that will be trimmed
dateYes
dueDateNo
descriptionNoa string that will be trimmed
verdictNoa string that will be trimmed
applicationNo
companyNoa string that will be trimmed
locationNoa string that will be trimmed
participantsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesThe successful tool result. The same value is also serialized as JSON in the text content for clients that do not read structuredContent.
warningsNoOptional agent-visible warnings about degraded result fidelity. Omitted when the server returned the documented happy-path payload.
Behavior5/5

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

The description discloses multiple behavioral traits beyond annotations: increments RVE sequence, attaches to candidate reviews collection, defaults dueDate, and recruit-enables the person if needed. Annotations provide only readOnlyHint and destructiveHint, so the description adds significant value.

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?

The description is a single sentence packed with specific details, front-loaded with the purpose, and contains no extraneous words. Every clause adds value.

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?

Given the tool's complexity (10 parameters, 3 required) and the presence of an output schema, the description covers key behaviors and internal side effects. It does not explain all parameters but is sufficient for understanding the tool's primary actions.

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?

The description adds meaning to two parameters (description format as Huly markup, dueDate default) but does not address the other eight parameters. Schema coverage is 60%, so the description partially compensates but not fully.

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 creates a recruiting review/interview, specifying the verb 'Create' and the resource 'Recruiting review.' It distinguishes from siblings like create_recruiting_applicant by mentioning internal actions like incrementing RVE sequence and attaching to candidate reviews.

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?

The description implies usage for creating reviews but does not explicitly state when to use this tool over alternatives like create_recruiting_opinion or when not to use it. No comparative guidance is provided.

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/dearlordylord/huly-mcp'

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