Jobero job search

Quick job match

quick_job_search

The single best current role for a profile, with a tailored CV and cover letter, in minutes rather than an hour. $2.50 in USDC. Use this when you want one answer fast; use start_job_search when you want a shortlist of 7 to choose from. With no credit it returns an x402 PaymentRequired; retry the same call with the signed payment in _meta["x402/payment"].

Input Schema

TableJSON Schema

Name	Required	Description
`cv_json`	No	The job seeker's existing CV as structured data, in the JSON Resume schema (jsonresume.org): basics, work, education, skills. Prefer this when you hold the CV as data — you do not need to render a file. Supply either cv_json or cv_base64
`cv_type`	No	Format of cv_base64: "pdf", "docx" or "txt". Ignored when cv_json is supplied
`profile`	Yes	Who the job seeker is and what they want. Every field shapes matching, so guessing is worse than asking
`cv_base64`	No	The job seeker's existing CV as a file, base64 encoded. PDF, DOCX or plain text, up to 10MB. Use cv_json instead if you have the CV as data rather than a file

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present only on failure, e.g. "unauthorized" or "payment_required"
`run_id`	No	Pass this to get_search_status to poll
`status`	No	Run state at the moment of starting, normally "running"
`message`	No	What happens next and roughly when, or what to do about the error
`credits_remaining`	No	Credits left for this product after the spend

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false), the description discloses key behaviors: the $2.50 USDC cost, the x402 PaymentRequired response when credit is insufficient, and the exact retry mechanism via _meta["x402/payment"]. This is meaningful behavioral context not present in the structured metadata.

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 long, front-loaded with the core purpose, then cost, usage alternatives, and payment retry behavior. There is no filler or redundant repetition of schema fields; every sentence adds distinct value.

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?

Given that an output schema exists and the input schema documents the 4 parameters thoroughly, the description covers the remaining contextual needs: cost, speed, choice between tools, and payment failure handling. It is complete for this complexity level.

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%, and the schema already provides detailed parameter descriptions for profile, cv_json, cv_base64, and cv_type. The tool description itself adds no parameter-specific semantics beyond referring to 'a profile', so the baseline score of 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 clearly states the tool returns 'the single best current role for a profile, with a tailored CV and cover letter' – a specific verb and resource. It distinguishes itself from the sibling tool start_job_search by contrasting the single result with a 7-option shortlist.

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?

Explicit usage guidance is given: 'Use this when you want one answer fast; use start_job_search when you want a shortlist of 7 to choose from.' It also provides error-handling instructions for the payment-required case, including how to retry with the signed payment.

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.

TDQS

A4.1/5.0

Disambiguation5/5

Each tool serves a distinct purpose: pricing, search initiation (quick vs full), status retrieval, and agent registration. The two search tools are explicitly differentiated by speed and output size, so there is no ambiguity.

Naming Consistency4/5

Most tools follow a verb_noun pattern (get_pricing, get_search_status, register_agent, start_job_search), but 'quick_job_search' uses an adjective_noun construction. The naming is consistent in style (lowercase snake_case) and generally predictable, with only one minor deviation.

Tool Count5/5

Five tools is well-scoped for a focused job search service, covering core operations without unnecessary redundancy. Each tool earns its place.

Completeness4/5

The tool set covers the essential workflow: registration, pricing, starting searches, and retrieving results. Minor gaps such as profile management or search history are not critical for the core purpose, making it reasonably complete.

Resources

Need Help?