jobspipe.dev WebMCP audit

audited Aug 28, 2026in 5s
63/ 100

4 tools registered. Strongest in usefulness, weakest in human experience.

WebMCP use69
Usefulness95
Human experience0
about:blank

No agent run recorded yet.

No steps recorded

Tools

/
search_job_postings: fail

search_job_postings

Search live job postings from the JobsPipe dataset. Returns normalized rows (title, budget, skills, client country, posted date) from the public Jobs API. The first 100 results are available without authentication.Takes an action on the site.
pagehttps://jobspipe.dev/
implementation
viaimperative
entry pointprovideContext
registered after631ms
executepresent
api surface
limitoptional
offsetoptional
sortoptional
orderoptional
annotations
read onlynot declared
destructivenot declared
idempotentnot declared
open worldnot declared
untrusted contentnot declared
titlenot declared
2 findings
failAnnotations present
0 / 4
4 of 4 tools declare no readOnlyHint, so an agent cannot tell a read from a write without guessing from the name.
search_job_postings, scan_company_tech_stack, get_api_catalog, navigate_to_page
fix
{
  name: "search_job_postings",
  annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true }
}
warningHuman parity
0 / 8
4 of 4 tools run through the JavaScript API with no visible counterpart, so the person co-browsing cannot see what the agent is offered. Declarative forms (or at least a title annotation) close the gap.
search_job_postings, scan_company_tech_stack, get_api_catalog, navigate_to_page
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="search_job_postings" tooldescription="...">
  <!-- the same action, as UI -->
</form>
tool json
{
  "name": "search_job_postings",
  "description": "Search live job postings from the JobsPipe dataset. Returns normalized rows (title, budget, skills, client country, posted date) from the public Jobs API. The first 100 results are available without authentication.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "limit": {
        "type": "integer",
        "minimum": 1,
        "maximum": 200,
        "description": "Number of postings to return (max 200)."
      },
      "offset": {
        "type": "integer",
        "minimum": 0,
        "description": "Number of postings to skip for pagination."
      },
      "sort": {
        "type": "string",
        "enum": [
          "posted_on",
          "title",
          "budget",
          "hourly_min",
          "proposals",
          "client_total_spent",
          "client_rating",
          "client_country",
          "tier"
        ],
        "description": "Field to sort by."
      },
      "order": {
        "type": "string",
        "enum": [
          "asc",
          "desc"
        ],
        "description": "Sort direction."
      }
    },
    "required": []
  },
  "annotations": {}
}
Showing search_job_postings

Findings

WebMCP use

69 / 100 · weight 50
passTools registered
4 / 4
4 tools registered across 1 page.
failReal-browser eligible
0 / 8
The page's code registers these tools, but a real visitor's browser does not get them yet: WebMCP needs a native modelContext or a current origin trial token, and this page has neither.
passRegistration timing
4 / 4
Every measured tool registered within 630.7000000476837ms of navigation.
toolget_api_catalog
passCanonical entry point
4 / 4
All 4 tools register on the canonical document.modelContext entry point.
passSchema validity
5 / 5
All 4 tools declare a structurally valid object input schema.
passSchema quality
4 / 4
All 4 tool schemas describe their parameters and stay within Chrome's size guidance.
passStub detection
5 / 5
All 4 tools declare an execute handler.
failAnnotations present
0 / 4
4 of 4 tools declare no readOnlyHint, so an agent cannot tell a read from a write without guessing from the name.
toolsearch_job_postings
search_job_postings, scan_company_tech_stack, get_api_catalog, navigate_to_page
fix
{
  name: "search_job_postings",
  annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true }
}
not applicableAnnotation mismatch
0 / 3
No tool declares a readOnlyHint, so there is no safety claim to contradict.
not applicableUntrusted content hint
0 / 2
No tool's contract suggests it returns text written by somebody other than the site, so there is nothing to flag as untrusted.
passRegistration errors
2 / 2
No tool registration threw during the capture.
warningToolchange coherence
1 / 2
4 tools were registered but the page never dispatched a toolchange event, so an agent subscribed to registry updates never learns they exist.
fix
document.modelContext.dispatchEvent(new Event("toolchange"));
not applicableInjection surface
0 / 3
The injection-surface model hop returned no usable result, so tool contracts were not reviewed for injection surface.

Usefulness

95 / 100 · weight 30
warningNaming quality
1.5 / 2
Tool naming makes selection harder than it needs to be: 2 names do not start with a verb (scan_company_tech_stack).
toolscan_company_tech_stack
fix
{ name: "scan_company_tech_stack" /* short, unique, verb-based */ }
not applicableDescription quality
0 / 6
The description-quality model hop returned no usable result, so descriptions were not rated.
not applicableTool selection
0 / 14
The tool-selection model hop returned no usable result.
passCoverage vs. site type
8 / 8
The tool set covers the whole core docs flow: search or browse the catalog, read a page or article, navigate the documentation tree.

Human experience

0 / 100 · weight 20
warningHuman parity
0 / 8
4 of 4 tools run through the JavaScript API with no visible counterpart, so the person co-browsing cannot see what the agent is offered. Declarative forms (or at least a title annotation) close the gap.
toolsearch_job_postings
search_job_postings, scan_company_tech_stack, get_api_catalog, navigate_to_page
fix
<!-- Give the tool a visible counterpart: a declarative form is one the person can see and use too. -->
<form toolname="search_job_postings" tooldescription="...">
  <!-- the same action, as UI -->
</form>
not applicablePage experience
0 / 12
The page-experience model hop returned no usable result, so the page was not graded.

Tool selection

The tool-selection model hop returned no usable result.
how this was captured
chrome
148.0.7778.96
capture shim
v1
spec snapshot
2026-08
mode
fast
pages
1
tools
4
run time
5s
finished
Aug 28, 2026