Skip to main content
Glama

Jobero job search

by ai.jobero
OverviewDiscussionsAdmin

Check a search

get_search_status
Read-onlyIdempotent

Progress of a search, and the matched roles with the reason each was picked once it finishes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
run_idNoThe run_id returned by start_job_search or quick_job_search. Omit to get the most recent run for this account

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
doneNoTrue once the run has finished, whether or not it found anything
planNoWhich product this run was: one_off or agent_quick
errorNoPresent only on failure, e.g. "unauthorized" or "payment_required"
run_idNo
statusNorunning, success, no_matches or failed
matchesNoThe delivered roles, each with its tailored documents. Absent until the run succeeds
messageNoProgress in plain language while running, or what to do about the error
started_atNo
finished_atNo
target_jobsNoHow many roles this run is meant to deliver

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / run_id / description
      Previous value: -"Omit to get the most recent run for this account"New value: +"The run_id returned by start_job_search or quick_job_search. Omit to get the most recent run for this account"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "done": {
+      "description": "True once the run has finished, whether or not it found anything",
+      "type": "boolean"
+    },
+    "error": {
+      "description": "Present only on failure, e.g. \"unauthorized\" or \"payment_required\"",
+      "type": "string"
+    },
+    "finished_at": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "matches": {
+      "description": "The delivered roles, each with its tailored documents. Absent until the run succeeds",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "company": {
+            "description": "Hiring company",
+            "type": "string"
+          },
+          "documents": {
+            "anyOf": [
+              {
+                "additionalProperties": false,
+                "properties": {
+                  "cover_letter_markdown": {
+                    "anyOf": [
+                      {
+                        "type": "string"
+                      },
+                      {
+                        "type": "null"
+                      }
+                    ],
+                    "description": "A cover letter written for this specific role, as markdown"
+                  },
+                  "cv_markdown": {
+                    "anyOf": [
+                      {
+                        "type": "string"
+                      },
+                      {
+                        "type": "null"
+                      }
+                    ],
+                    "description": "The CV rewritten for this specific role, as markdown"
+                  }
+                },
+                "required": [
+                  "cv_markdown",
+                  "cover_letter_markdown"
+                ],
+                "type": "object"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "The tailored documents for this role. Null while the run is still going, and on older runs that predate document return"
+          },
+          "match_reason": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Why this role was picked for this profile"
+          },
+          "rank": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Position in the delivered set, 1 is the strongest match"
+          },
+          "score": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ],
+            "description": "Fit score out of 100, higher is better"
+          },
+          "title": {
+            "description": "Job title as advertised",
+            "type": "string"
+          },
+          "url": {
+            "description": "Link to the live posting",
+            "type": "string"
+          }
+        },
+        "required": [
+          "title",
+          "company",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "message": {
+      "description": "Progress in plain language while running, or what to do about the error",
+      "type": "string"
+    },
+    "plan": {
+      "description": "Which product this run was: one_off or agent_quick",
+      "type": "string"
+    },
+    "run_id": {
+      "type": "string"
+    },
+    "started_at": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "status": {
+      "description": "running, success, no_matches or failed",
+      "type": "string"
+    },
+    "target_jobs": {
+      "description": "How many roles this run is meant to deliver",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description adds useful behavioral context: it reports progress while a search is ongoing and matched roles with reasons once complete. This clarifies the two-phase behavior, which is not deducible from the annotations. It does not describe edge cases like error handling or timeouts, but it adds meaningful transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely brief, but it is not a complete sentence ('Progress of a search, and the matched roles...'). It front-loads the core purpose and uses no unnecessary words. However, the fragmentary grammar and lack of a clear verb slightly reduce clarity, so it is concise but not perfectly structured.

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?

Given the tool's simplicity (1 optional parameter, no nested objects, and an output schema), the description adequately conveys the tool's function. Annotations cover read-only and idempotent behavior, and the output schema likely documents return details. The main missing context is a clearer statement of when to call it, but overall it is sufficiently complete for an agent to invoke correctly.

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 for parameters is 100%; the run_id parameter is fully described in the schema including that it is optional and can be omitted for the most recent run. The description text itself adds no parameter-specific meaning beyond that, so it meets the baseline but does not exceed it.

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 title 'Check a search' and description 'Progress of a search, and the matched roles with the reason each was picked once it finishes' clearly identify a resource (search) and action (check/status). It distinguishes itself from sibling tools like start_job_search and quick_job_search by focusing on examining an existing search's progress and results rather than initiating one.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not explicitly state when to use this tool versus alternatives. It does not mention that it should be called after start_job_search or quick_job_search, nor does it exclude other scenarios. The only usage context comes from the schema's parameter description, not from the description itself.

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 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.

Resources