Crawlora MCP

tes_job_search

Read-only

Search Tes teaching jobs with location, salary, contract, and live position or subject facets. Use tes_job_detail for one vacancy or tes_school_search to find an employer.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tes_job_search"
  }
}

Input Schema

Name	Required	Description
`page`	No	One-based page
`sort`	No	Sort order. Documented values: relevance, newest, distance.
`subject`	No	Comma-separated subject label(s) -- see the endpoint markdown
`keywords`	No	Job title or keyword
`location`	No	Free-text place name resolved via Tes's own location autocomplete
`position`	No	Comma-separated position category label(s) -- see the endpoint markdown
`page_size`	No	Results per page
`workplace`	No	Comma-separated workplace/organisation-type label(s) -- see the endpoint markdown
`salary_min`	No	Minimum advertised salary, in the searched market's local currency
`radius_miles`	No	Search radius around location, in miles. Documented values: 3, 5, 10, 15, 20, 30, 50, 70, 100, 500.
`contract_term`	No	Contract term. Documented values: Permanent, Fixed Term, Casual, Maternity Cover, Temporary, Supply.
`contract_type`	No	Contract type. Documented values: Full Time, Part Time.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedOct 7, 2026

addedInput schema / properties / contract_term / description

Added value: +"Contract term. Documented values: Permanent, Fixed Term, Casual, Maternity Cover, Temporary, Supply."

addedInput schema / properties / contract_type / description

Added value: +"Contract type. Documented values: Full Time, Part Time."

addedInput schema / properties / keywords / description
```
Added value: +"Job title or keyword"
```

addedInput schema / properties / location / description

Added value: +"Free-text place name resolved via Tes's own location autocomplete"

addedInput schema / properties / page / description
```
Added value: +"One-based page"
```
addedInput schema / properties / page_size / description
```
Added value: +"Results per page"
```

addedInput schema / properties / position / description

Added value: +"Comma-separated position category label(s) -- see the endpoint markdown"

addedInput schema / properties / radius_miles / description

Added value: +"Search radius around location, in miles. Documented values: 3, 5, 10, 15, 20, 30, 50, 70, 100, 500."

addedInput schema / properties / salary_min / description

Added value: +"Minimum advertised salary, in the searched market's local currency"

addedInput schema / properties / sort / description

Added value: +"Sort order. Documented values: relevance, newest, distance."

addedInput schema / properties / subject / description

Added value: +"Comma-separated subject label(s) -- see the endpoint markdown"

addedInput schema / properties / workplace / description

Added value: +"Comma-separated workplace/organisation-type label(s) -- see the endpoint markdown"

First observedOct 5, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and open-web profile are covered. The description adds that the search works over live facets and position/subject labels, which is useful context. It doesn't describe pagination or result behavior, but with a read-only, open-world search that's a minor gap and the annotations carry the safety load.

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, front-loaded with the primary purpose, followed immediately by the sibling-routing guidance. No filler and nothing redundant.

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?

For a read-only, open-world, 12-param faceted search tool with a full schema and an output schema, the description covers the scope, the facets, and the sibling routing. Nothing critical for correct invocation 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 the schema already documents all 12 parameters including enum-like documented values. The description mentions the facet dimensions (location, salary, contract, position, subject) but adds no syntax or value details beyond what the schema provides, so the baseline of 3 is correct.

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 names a specific verb (Search) and resource (Tes teaching jobs) and lists the facet dimensions covered (location, salary, contract, live position/subject). It explicitly distinguishes itself from the sibling tes_job_detail (one vacancy) and tes_school_search (find an employer).

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?

It gives explicit routing: use tes_job_search for faceted job search; use tes_job_detail for one vacancy; use tes_school_search to find an employer. This is a textbook when-to-use/alternative pattern.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?