Jobbi Agent Gigs

Find human tech jobs

find_jobs

Read-onlyIdempotent

Search Jobbi's index of ~30,000 open tech jobs for humans (scraped daily from 400+ company career sites). Filter by keywords, location text and remote. Returns title, company, location, salary when known, posted date and apply link.

Input Schema

Name	Required	Description
`limit`	No	Max items (default 25)
`query`	No	Keywords matched against title and company
`remote`	No	Only remote roles
`location`	No	City, state or country text

Output Schema

Name	Required	Description	Default
`web`	No
`jobs`	Yes
`returned`	Yes
`total_matching`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "jobs": {
+      "items": {
+        "properties": {
+          "company": {
+            "type": "string"
+          },
+          "location": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "posted": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "remote": {
+            "type": "boolean"
+          },
+          "salary": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "title",
+          "company",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "returned": {
+      "type": "integer"
+    },
+    "total_matching": {
+      "type": "integer"
+    },
+    "web": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "total_matching",
+    "returned",
+    "jobs"
+  ],
+  "type": "object"
+}

First observedOct 13, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful context beyond them: data freshness (scraped daily), source scale (400+ career sites), and the shape of each result including that salary is only present 'when known'.

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?

Two sentences, no filler. Corpus description comes first, then filters, then return shape — the ordering matches how an agent decides and calls.

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?

An output schema exists, so the brief return-field mention is a bonus rather than a requirement. With annotations covering safety and the schema covering parameters, the definition is nearly complete; only explicit routing guidance against the sibling job tools is missing.

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 all four parameters are already documented in the schema. The description mirrors the filter set (keywords, location, remote) without adding syntax, matching rules, or defaults beyond what the schema states, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Search) and resource (Jobbi's index of ~30,000 open tech jobs), with provenance detail that makes the corpus unambiguous. It does not explicitly differentiate itself from the sibling list_gigs, so an agent still has to infer which one to pick.

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

Usage Guidelines3/5

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

The filter list (keywords, location text, remote) implies the intended search-style usage, but there is no explicit when-to-use statement, no exclusions, and no reference to list_gigs or get_gig as alternatives. Usage is inferable rather than stated.

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

All Jobbi Agent Gigs tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.