Skip to main content
Glama

Human Pages

by io.github.human-pages-ai

register_agent

Register a new agent on Human Pages. Returns an API key (hp_...) that you MUST save — it cannot be retrieved later. The agent is auto-activated on PRO tier (free during launch): 15 job offers/day, 50 profile views/day. Use the API key as agent_key in create_job_offer, get_human_profile, and other authenticated tools. Typical first step before hiring.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesDisplay name for your agent (e.g., "Acme AI Assistant")
accept_tosYesYou must pass true to confirm you accept the Human Pages Terms of Use (https://humanpages.ai/terms). Required.
descriptionNoBrief description of what your agent does (max 500 chars)
webhook_urlNoWebhook URL for receiving platform events (new job matches, status changes, announcements). Must be a public HTTPS endpoint.
website_urlNoYour website URL (can be verified later for a trust badge)
contact_emailNoContact email for the agent operator
wallet_addressNoOptional EVM wallet address (0x...) for USDC payments. Can also be set later with set_wallet. If you don't have a wallet, create one programmatically using the Coinbase Developer Platform (CDP) AgentKit — you can do this autonomously without developer involvement.

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description fully owns the transparency burden. It discloses the most critical behavioral trait: the API key can only be retrieved once and must be saved immediately. It also transparently states the auto-activation, quotas, and the free launch tier, giving the agent all necessary operational expectations.

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?

Three sentences, each delivering essential information: what it does, critical warning about the API key, and post-registration usage. The description is front-loaded and every sentence adds value without padding.

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?

For a registration tool with no output schema, the description covers the core context: the return value (API key), its irrecoverability, the activation tier with quotas, and how to integrate with other tools. It could mention error cases or follow-up verification (e.g., check get_activation_status), but for a typical first-step creator, this is sufficiently complete.

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 seven parameters. The description adds no additional parameter-specific semantics beyond what's in the schema. It does mention the API key usage, but that's an output concern, not a parameter detail. 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?

The description clearly states the tool's function: "Register a new agent on Human Pages." It distinguishes from siblings like register_as_arbitrator by focusing on the general agent registration flow, and it frames itself as "Typical first step before hiring," which differentiates it from other setup tools.

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?

It provides clear context for when to use the tool: as a first step before hiring, and it explains how to use the returned API key in subsequent authenticated tools. While it doesn't explicitly name alternatives to avoid, it implicitly signals that separate activation (e.g., claim_free_pro_upgrade) may be unnecessary due to auto-activation on PRO tier.

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