Skip to main content
Glama

Human Pages

by io.github.human-pages-ai

get_listings

Browse open job listings on the public board. Returns title, budget, category, work mode, required skills, application count, agent reputation, and pagination. Filter by skill, category, work_mode, budget range, or location. Paginated: use page/limit params (default 20, max 50). Response includes total count and total pages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNoLatitude for location-based filtering
lngNoLongitude for location-based filtering
pageNoPage number (default: 1)
limitNoResults per page (default: 20, max: 50)
skillNoFilter by required skill (comma-separated for multiple, e.g., "photography,editing")
radiusNoRadius in km for location-based filtering
categoryNoFilter by category
work_modeNoFilter by work mode
max_budgetNoMaximum budget in USD
min_budgetNoMinimum budget in USD

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses return fields, filter capabilities, pagination defaults/max, and response counts (total and pages). It implies a read-only browse operation but does not explicitly state side-effect-free status or authentication needs; still, it is quite transparent for a list-reading tool.

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?

The description is three sentences with no fluff. Each sentence serves a purpose: first states purpose and output fields, second lists filters, third covers pagination. It is appropriately sized and front-loaded.

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?

No output schema exists, so the description must explain return values, which it does by listing return fields and pagination metadata. It covers all filter dimensions and pagination behavior. Missing details like error handling or optionality of location parameters are minor given the tool's simplicity.

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 coverage is 100%, so the baseline is 3. The description reiterates filter types and pagination defaults that are already in the schema, adding no new parameter-specific semantics beyond reinforcing how they are used together (e.g., location parameters implied by 'location').

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 the tool 'Browse open job listings on the public board' with a specific verb, resource, and scope. It lists return fields and distinguishes itself from the singular sibling 'get_listing' through the plural 'listings' and browsing intent.

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?

The description conveys clear context: this is for browsing and filtering multiple listings on the public board. However, it does not explicitly mention alternatives (e.g., 'use get_listing for a single listing') or provide when-not-to-use guidance, so it lacks explicit exclusions.

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

All Human Pages toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation4/5

Most tools have clearly distinct purposes (e.g., get_human vs get_human_profile differ by access level, get_listing vs get_listings by specificity). There is minor overlap between check_humanity_status and get_human (both return verification info), and the deprecated no-op claim_free_pro_upgrade adds slight clutter, but descriptions otherwise disambiguate well.

Naming Consistency5/5

All 40 tools follow a consistent snake_case verb_noun pattern (e.g., create_listing, get_job_status, start_stream, submit_verdict). No camelCase or mixed conventions exist; even compound actions like make_listing_offer and leave_review fit the established pattern.

Tool Count2/5

With 40 tools, this is far beyond the 16-25 'heavy' range and into the 'too many' category. While the platform covers a broad domain (hiring, listings, streams, escrow, activation), this many tools could be split into smaller focused servers for maintainability and agent selection clarity.

Completeness4/5

The surface covers the core lifecycle well: search, hire, pay, communicate, approve, review. However, there is no generic cancel_job tool for regular jobs (only stop_stream for streams) and no update_listing to edit an existing listing, leaving small but navigable gaps in lifecycle management.

Resources