Jobero job search

Get pricing

get_pricing

Read-onlyIdempotent

What a Jobero search costs and how to pay for it, in card and stablecoin terms. No auth required.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`x402`	Yes	Stablecoin payment terms, null if x402 is not configured
`packs`	Yes	Buyable credit packs
`service`	Yes	Service name
`products`	Yes	The two things Jobero sells
`card_checkout`	Yes	URL for card payment
`free_searches`	Yes	Always false: registration grants no credits
`credits_are_per_product`	Yes	Always true: a quick credit cannot pay for a full search

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 1, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "card_checkout": {
+      "description": "URL for card payment",
+      "type": "string"
+    },
+    "credits_are_per_product": {
+      "description": "Always true: a quick credit cannot pay for a full search",
+      "type": "boolean"
+    },
+    "free_searches": {
+      "description": "Always false: registration grants no credits",
+      "type": "boolean"
+    },
+    "packs": {
+      "description": "Buyable credit packs",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "buys": {
+            "description": "Which product these credits are valid for: search or quick",
+            "type": "string"
+          },
+          "credits": {
+            "description": "How many runs the pack buys",
+            "type": "number"
+          },
+          "description": {
+            "type": "string"
+          },
+          "pack": {
+            "description": "Pack code to pass to checkout or to pay for over x402",
+            "type": "string"
+          },
+          "price": {
+            "description": "Human-readable price",
+            "type": "string"
+          }
+        },
+        "required": [
+          "pack",
+          "credits",
+          "price",
+          "buys",
+          "description"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "products": {
+      "description": "The two things Jobero sells",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "price": {
+            "description": "Human-readable price",
+            "type": "string"
+          },
+          "tool": {
+            "description": "Which tool buys this product",
+            "type": "string"
+          },
+          "typical_time": {
+            "description": "How long delivery usually takes",
+            "type": "string"
+          },
+          "unit": {
+            "description": "What one purchase delivers",
+            "type": "string"
+          }
+        },
+        "required": [
+          "tool",
+          "unit",
+          "price",
+          "typical_time"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "service": {
+      "description": "Service name",
+      "type": "string"
+    },
+    "x402": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "asset": {
+              "description": "Token accepted, USDC",
+              "type": "string"
+            },
+            "how": {
+              "description": "How to complete the payment loop",
+              "type": "string"
+            },
+            "network": {
+              "description": "Chain the payment settles on",
+              "type": "string"
+            },
+            "pay_to": {
+              "description": "Receiving address",
+              "type": "string"
+            },
+            "prices": {
+              "additionalProperties": {
+                "type": "string"
+              },
+              "description": "Pack code to atomic USDC amount",
+              "propertyNames": {
+                "type": "string"
+              },
+              "type": "object"
+            }
+          },
+          "required": [
+            "network",
+            "asset",
+            "pay_to",
+            "prices",
+            "how"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Stablecoin payment terms, null if x402 is not configured"
+    }
+  },
+  "required": [
+    "service",
+    "products",
+    "packs",
+    "credits_are_per_product",
+    "card_checkout",
+    "x402",
+    "free_searches"
+  ],
+  "type": "object"
+}

First observedJul 31, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, but the description adds valuable behavioral context: no authentication is required, and it specifies the output will cover card and stablecoin terms.

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?

A single sentence that front-loads the purpose ('What a Jobero search costs') and adds one key qualifier. No wasted words.

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 parameters and an output schema available, the description sufficiently covers the tool's purpose and key usage context. Nothing critical is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the baseline of 4 applies. The description does not need to explain parameter semantics.

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 provides cost and payment details for a Jobero search, distinguishing it from sibling tools like get_search_status or quick_job_search.

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 clearly implies when to use it (to understand pricing and payment options), and notes 'No auth required' as a usage condition. It does not explicitly exclude alternatives, but siblings are obviously different in function.

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?