Skip to main content
Glama
profilesearch

GoHireHumans

Official
by profilesearch
OverviewSchemaSourceRelated ServersDiscussionsAdmin

search_workers

Read-only

Find and compare workers on GoHireHumans by skills, category, price, and rating. Returns one result per provider with name, rating, price range, and service titles for comparison.

Instructions

Find workers (people or agents offering services) on GoHireHumans, with one result per provider instead of one per listing. Read-only; no API key needed. Searches public service listings by skills, category, price and minimum rating, then groups the matching listings by provider; each result shows the provider's name, rating, the price range of those matching listings and up to three of their service titles. Providers are listed in order of their highest-rated matching listing; the rating shown is the provider's profile rating when one exists, so it can differ from that order. Use this to compare providers. Use search_services when you need listing IDs to hire, and get_recommended to rank options for a task description.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of providers to return (default 10, max 50)
skillsNoSkills or keywords to match against listing titles, descriptions and tags (e.g., ['Python', 'data analysis']); combined into one text search
categoryNoFilter by category slug from get_categories
min_ratingNoMinimum profile/listing average rating (1-5); applied locally to returned services (unrated workers excluded), fetching more pages until enough providers match
max_hourly_rateNoMaximum listed price or hourly rate in USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.1.0
    • changedInput schema / properties / category / description
      Previous value: -"Filter by service category"New value: +"Filter by category slug from get_categories"
    • changedInput schema / properties / limit / description
      Previous value: -"Number of results (default 10, max 50)"New value: +"Number of providers to return (default 10, max 50)"
    • changedInput schema / properties / max_hourly_rate / description
      Previous value: -"Maximum hourly rate in USD"New value: +"Maximum listed price or hourly rate in USD"
    • changedInput schema / properties / min_rating / description
      Previous value: -"Minimum profile/listing average rating (1-5); applied locally to returned services (unrated workers excluded)"New value: +"Minimum profile/listing average rating (1-5); applied locally to returned services (unrated workers excluded), fetching more pages until enough providers match"
    • changedInput schema / properties / skills / description
      Previous value: -"Required skills to search for (e.g., ['Python', 'data analysis'])"New value: +"Skills or keywords to match against listing titles, descriptions and tags (e.g., ['Python', 'data analysis']); combined into one text search"
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds real context beyond them: no API key is required, results are grouped by provider, ordering follows the highest-rated matching listing, and the displayed rating may come from the provider profile and thus disagree with the sort order. It does not cover pagination behavior when limit is raised, but the disclosure is well above the annotation baseline.

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?

Front-loads the core definition and the per-provider grouping before moving to filters, return shape, and sibling routing. Dense but every sentence carries information; slightly long as a single unbroken paragraph.

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, the description compensates by describing the return shape (provider name, rating, price range, up to three service titles) and the ordering caveat. Combined with the sibling routing and auth note, 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 all five parameters including the min_rating local-filter nuance. The description only summarizes the filter dimensions ('skills, category, price and minimum rating') without adding syntax or format detail beyond the schema, so the baseline 3 applies.

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 ('Find workers (people or agents offering services)') plus the key aggregation behavior ('one result per provider instead of one per listing'). It explicitly distinguishes itself from siblings search_services and get_recommended, so an agent can route correctly without opening schemas.

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?

Gives an explicit when-to-use ('Use this to compare providers') and names the two alternatives with the conditions that select them ('search_services when you need listing IDs to hire', 'get_recommended to rank options for a task description'). Nothing 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.

Deploy Server

Other Tools