Skip to main content
Glama

create_recruiting_vacancy

Creates a recruiting vacancy with name, description, type, company, location, due date, and privacy settings. Defaults owners to the current account and stores full description as collaborative markup.

Instructions

Create a Recruiting vacancy like the Huly UI: increments the vacancy sequence, stores fullDescription as markdown-backed collaborative markup, defaults members/owners to the current account, and creates vacancy type-data mixin {}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesa string that will be trimmed
shortDescriptionNoa string that will be trimmed
fullDescriptionNoa string that will be trimmed
typeNoa string that will be trimmed
companyNoa string that will be trimmed
locationNoa string that will be trimmed
dueToNo
privateNoWhether the created or updated Recruiting object should be private.

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.
Behavior4/5

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

The description discloses key behaviors not covered by annotations: increments sequence, stores fullDescription as collaborative markdown, defaults members/owners to current account, and creates a type-data mixin. This adds significant context beyond the readOnlyHint and destructiveHint flags.

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 a single sentence that packs multiple pieces of information efficiently. It could be split for readability, but it is not verbose. All sentences earn their place.

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 8 parameters and existing output schema, the description covers the main behavioral aspects (side effects, defaults, data handling). It does not mention the 'private' parameter's effect, but schema coverage is high enough to compensate.

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 high (88%), but the description adds semantic value: explains that fullDescription is markdown-backed, and members/owners are defaulted. This goes beyond the basic schema descriptions, though individual parameter explanations are not exhaustive.

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 'Create a Recruiting vacancy', using a specific verb and resource. It differentiates from sibling creation tools like create_recruiting_applicant by focusing on vacancies, and mentions UI analogy for clarity.

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?

Usage is implied as the standard creation tool for vacancies, but no explicit guidance on when to use this versus alternatives (e.g., update_recruiting_vacancy) is provided. No exclusions or prerequisites are mentioned.

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