Jobero job search

Register for an API key

register_agent

Create an agent identity and receive an API key. Registration is free and includes no free searches.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No	Display name for the account. Optional; the profile name is used on documents regardless
`email`	Yes	Email that will own the account and receive results. Must be the job seeker's own address, and must match cfg_email on every later search

Output Schema

TableJSON Schema

Name	Required	Description
`next`	No	Suggested next call
`note`	No
`email`	No	The address the account is registered to
`error`	No	Present only on failure, e.g. "unauthorized" or "payment_required"
`api_key`	No	Bearer token for every later call. Shown once and never again
`message`	No	What to do about the error, when one is present
`owner_action_url`	No	Present only on account_owned_by_human. A person already owns this address, so no key can be issued here. Send them to this page to create one and paste it back

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 1, 2026

addedOutput schema / properties / owner_action_url

Added value: +{
+  "description": "Present only on account_owned_by_human. A person already owns this address, so no key can be issued here. Send them to this page to create one and paste it back",
+  "type": "string"
+}

Changed3 schema fields changedAug 1, 2026

changedInput schema / properties / email / description

Previous value: -"Email that will own the account and receive results"New value: +"Email that will own the account and receive results. Must be the job seeker's own address, and must match cfg_email on every later search"

addedInput schema / properties / name / description

Added value: +"Display name for the account. Optional; the profile name is used on documents regardless"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "api_key": {
+      "description": "Bearer token for every later call. Shown once and never again",
+      "type": "string"
+    },
+    "email": {
+      "description": "The address the account is registered to",
+      "type": "string"
+    },
+    "error": {
+      "description": "Present only on failure, e.g. \"unauthorized\" or \"payment_required\"",
+      "type": "string"
+    },
+    "message": {
+      "description": "What to do about the error, when one is present",
+      "type": "string"
+    },
+    "next": {
+      "description": "Suggested next call",
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedJul 31, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations are all false, providing minimal safety or mutation context. The description adds useful behavioral information: 'Registration is free and includes no free searches,' and that it creates an identity and returns an API key. Yet it does not disclose potential caveats like rate limits, key activation, or the relationship between the key and later searches.

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 two sentences long, front-loaded with the main purpose and followed by a relevant caveat. Every word earns its place—no filler or repetition.

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 simple registration tool with an output schema and full parameter coverage, the description covers the essentials: what it creates, what it returns, and cost-related behavior. It does not need to explain output format given the output schema. A minor gap is the lack of explicit guidance on how the API key integrates with sibling tools, but this is not critical.

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% with descriptive parameter details (email must be job seeker's own address, must match cfg_email later). The description adds no parameter-level meaning, so it does not improve on the schema. 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?

The description uses a specific verb ('Create') and identifies the resource ('agent identity and receive an API key'). It clearly distinguishes the tool from siblings like search and pricing tools, and the extra detail about free registration and no free searches reinforces its unique purpose.

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 context is clear: this tool is for registering to get an API key, distinct from the search and pricing siblings. However, it does not explicitly state when to use it versus alternatives, nor does it provide exclusions or prerequisites beyond the schema's email constraint.

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

All Jobero job search tools Inspect

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.

Resources

Need Help?