Jobiba Hiring: Post Jobs, Screen Applicants & Source Talent

Post a Jobiba job

post_job

Destructive

Create an employer-owned job through Jobiba validation and plan limits.

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": {
      "title": "<title>",
      "description": "<description>",
      "location": "<location>"
    },
    "name": "post_job"
  }
}

Input Schema

Name	Required	Description
`city`	No
`state`	No
`title`	Yes	Job title.
`skills`	No
`country`	No
`jobType`	No
`applyUrl`	No	Optional https URL for external applications.
`location`	Yes	Display location, e.g. 'Pune, India'.
`expiresAt`	No	Optional ISO date when the job closes.
`salaryMax`	No
`salaryMin`	No
`remoteType`	No
`description`	Yes	Full job description (responsibilities, requirements, benefits).
`salaryPeriod`	No
`salaryCurrency`	No
`experienceLevel`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already disclose destructiveHint=true, openWorldHint=true, idempotentHint=false and readOnlyHint=false, so the mutation profile is known. The description adds real value beyond that by flagging two behavioral gates — Jobiba-side validation and plan/quota limits — meaning the call can fail for reasons unrelated to input shape. It does not say what those limits are, what happens to a rejected submission, or what the created entity looks like.

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?

A single front-loaded sentence with no filler; the action and its two governing constraints arrive immediately. It is lean to the point of being under-built for a 16-parameter mutation, though nothing in it is wasted.

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?

For a 16-parameter, non-idempotent, open-world write with no output schema, one sentence leaves too much unresolved: which fields drive validation, how salary fields interact, what the plan limit failure mode is, and what is returned. The two constraints mentioned are named but not explained.

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?

Zero parameters defined; nothing to disambiguate.

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?

States a specific verb and resource ("Create ... job") and narrows scope with "employer-owned," which separates it from a generic job creation action and hints at a distinct path from draft_job_post. It stops short of naming or contrasting any sibling tool, so the differentiation is only implicit.

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 explicit when-to-use or when-not-to-use guidance. The phrase "through Jobiba validation and plan limits" implies this is the gated/publishing path rather than a drafting path, but the agent is never told to prefer draft_job_post or review_job_post first, nor what prerequisites (plan tier, employer identity) must hold.

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

All Jobiba Hiring: Post Jobs, Screen Applicants & Source Talent 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.