Selenios

Draft job position with AI

generate_job_draft

Read-onlyIdempotent

Generate an AI draft of a job posting from a short free-text brief (e.g. "Backend Engineer with 10 years of Node"). Nothing is created or saved. Each call runs an AI generation that takes several seconds and counts toward the organization's AI usage. Returns the drafted fields (title, description HTML, modality, salary, locations, benefits) plus the organization name and description. Optionally starts from an existing job position (baseJobDescriptionId).

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": {
      "brief": "<brief>"
    },
    "name": "generate_job_draft"
  }
}

Input Schema

Name	Required	Description	Default
`brief`	Yes	Free-text description of the role to draft
`baseJobDescriptionId`	No	Existing job position to use as the starting point

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnly, idempotent, non-destructive) by disclosing that each call triggers a real AI generation, takes several seconds, and consumes the organization's AI usage quota. It also confirms the no-side-effect claim in plain language, which is exactly the cost/latency context an agent needs before calling.

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 tightly packed sentences, front-loaded with the action and its no-save guarantee, then cost, then return shape, then the optional parameter. No filler or redundant restatement of the title.

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

Completeness5/5

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

There is no output schema, yet the description enumerates the returned fields (title, description HTML, modality, salary, locations, benefits, plus organization name/description), and it covers side effects, latency, and quota impact. Nothing material is missing for an agent to decide and call correctly.

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 is 3, but the description adds value by showing an example brief ('Backend Engineer with 10 years of Node') and framing baseJobDescriptionId as an optional starting point. The additions are modest but real, since they clarify what a good brief looks like rather than just repeating field names.

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 ('Generate an AI draft of a job posting') plus the input form ('short free-text brief'), and immediately disambiguates from the write-path sibling with 'Nothing is created or saved.' An agent can distinguish this from create_job_description without opening either 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?

Gives clear context for when to use it: a short free-text brief, optionally seeded from an existing job via baseJobDescriptionId. The 'nothing is created or saved' line implicitly routes persistence work to create_job_description, but no sibling is named explicitly, so the alternative is left to inference.

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

All Selenios tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?