Skip to main content
Glama
profilesearch

GoHireHumans

Official
by profilesearch
OverviewSchemaSourceRelated ServersDiscussionsAdmin

create_job

Publish a new job opening on GoHireHumans to collect worker applications. Requires owner approval and write API key; returns job ID to track status.

Instructions

Publish a new job post on GoHireHumans that workers can apply to. Get the account owner's approval of the title, description and budget first. Needs GOHIREHUMANS_AUTH_TOKEN or an API key with the write scope. The job is published immediately with status 'open', and workers with services in the same category may be notified. It does not hire anyone or charge anything: applicants are reviewed and hired on gohirehumans.com. This server cannot edit or close a job. Returns the new job ID and status; track it with get_job_status(job_id). To order an existing service listing instead, use hire_worker.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesJob title (e.g., 'Build a React landing page')
categoryYesCategory slug from get_categories (e.g., 'research', 'phone_call', 'data_entry')
budget_typeYesUse 'fixed'. Hourly jobs are not accepted right now and return an error.
descriptionYesPublic job description: the task, deliverables, deadline and anything a worker needs to know
budget_amountYesTotal budget in USD for a fixed-price job: greater than 0, in whole cents, at most 999,999.99
skills_requiredNoList of required skills (e.g., ['React', 'TypeScript', 'CSS'])

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.1.0
    • changedInput schema / properties / budget_amount / description
      Previous value: -"Budget in USD (total for fixed, per-hour for hourly)"New value: +"Total budget in USD for a fixed-price job: greater than 0, in whole cents, at most 999,999.99"
    • changedInput schema / properties / budget_type / description
      Previous value: -"Fixed price or hourly rate"New value: +"Use 'fixed'. Hourly jobs are not accepted right now and return an error."
    • changedInput schema / properties / category / description
      Previous value: -"Category slug (use get_categories to see options)"New value: +"Category slug from get_categories (e.g., 'research', 'phone_call', 'data_entry')"
    • changedInput schema / properties / description / description
      Previous value: -"Detailed job description with requirements and deliverables"New value: +"Public job description: the task, deliverables, deadline and anything a worker needs to know"
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial context beyond annotations: immediate publication with status 'open', possible worker notifications, no hiring or charging, and an explicit statement that this server cannot edit or close a job. It also discloses the auth requirement (GOHIREHUMANS_AUTH_TOKEN or write-scoped API key), which annotations do not cover.

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 front-loaded with purpose, then prerequisites, side effects, and alternatives in a logical order. It is a dense paragraph with no filler, though slightly long for a single tool.

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?

With no output schema present, the description compensates by stating the return value ('the new job ID and status') and how to track it. Combined with the side-effect, auth, and limitation disclosures, an agent has everything needed to call it correctly.

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 description coverage is 100%, so the schema already documents every parameter including the enum constraint on budget_type and the whole-cents budget rule. The description adds only the approval prerequisite for title/description/budget rather than new per-parameter meaning, so the baseline 3 is appropriate.

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 ('Publish a new job post on GoHireHumans') plus the effect on workers ('that workers can apply to'). It also distinguishes itself from the sibling hire_worker by naming that alternative outright.

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

Usage Guidelines5/5

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

Explicitly states the prerequisite (owner approval of title, description and budget) and routes the agent to the right sibling for a different task ('To order an existing service listing instead, use hire_worker'). It also points to get_job_status for follow-up, leaving nothing to inference.

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

Deploy Server

Other Tools