Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tes_job_search

Search Tes teaching jobs by keyword, location, salary, contract type, and more. Returns normalized listing details and live filter facet counts for refined job discovery.

Instructions

Search Tes teaching jobs. Searches Tes's (tes.com) teaching-jobs board. Returns normalized listing facts (title, employer, location, salary, contract terms/types) plus a short excerpt of the listing description, not the full long-form job-description copy, and the same live faceted-search breakdown (position/subject/workplace category trees with counts, plus contract type/term counts) the real search page renders as its filter sidebar. location is a free-text place name (a UK town/city, an international city, or a bare country name) resolved to coordinates via Tes's own location-autocomplete endpoint; omit for Tes's own default market, "United Kingdom". radius_miles selects the search radius around location. contract_type and contract_term are validated against Tes's own small, closed label sets. position, subject, and workplace are comma-separated passthrough filters -- Tes's own category labels are numerous and can change, so read a prior response's own facets.positions[].value (and facets.positions[].children[].value)/facets.subjects[].value/facets.workplaces[].children[].value for the live, current set rather than guessing. salary_min filters to jobs with an advertised salary at or above that amount (in the searched market's local currency); Tes's own filter panel offers only a minimum, no maximum.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoOne-based page
sortNoSort order
subjectNoComma-separated subject label(s) -- see the endpoint markdown
keywordsNoJob title or keyword
locationNoFree-text place name resolved via Tes's own location autocomplete
positionNoComma-separated position category label(s) -- see the endpoint markdown
page_sizeNoResults per page
workplaceNoComma-separated workplace/organisation-type label(s) -- see the endpoint markdown
salary_minNoMinimum advertised salary, in the searched market's local currency
radius_milesNoSearch radius around location, in miles
contract_termNoContract term
contract_typeNoContract type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.17.5
    • addedInput schema / properties / contract_term / enum
      Added value: +[
+  "Permanent",
+  "Fixed Term",
+  "Casual",
+  "Maternity Cover",
+  "Temporary",
+  "Supply"
+]
    • addedInput schema / properties / contract_type / enum
      Added value: +[
+  "Full Time",
+  "Part Time"
+]
    • addedInput schema / properties / radius_miles / enum
      Added value: +[
+  3,
+  5,
+  10,
+  15,
+  20,
+  30,
+  50,
+  70,
+  100,
+  500
+]
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "relevance",
+  "newest",
+  "distance"
+]
  2. Addedv1.16.2

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden, and it discloses important traits: it returns a short excerpt, not full copy; facets mirror the live page; location is resolved via Tes's autocomplete; and salary_min is in local currency with no maximum. It does not mention pagination behavior, auth, or error cases, so not a 5.

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 information-dense and front-loads the core purpose, with no filler. It is a single long paragraph that could be tightened or bulleted, and the first two clauses are slightly redundant, but every subsequent sentence earns its place.

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?

For a 12-parameter search tool with no annotations and no output schema, the description covers the high-risk parameter behaviors, defaults, response contents, and the facet-reading pattern. It omits exact output JSON structure, sorting/pagination defaults, and an explicit pointer to sibling detail/employer tools, so it is not fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Even though schema coverage is 100%, the description adds substantial meaning: location is free text with a specific default market, position/subject/workplace are passthrough filters whose label sets must be read from facets, contract fields are validated against closed sets, and salary_min uses the market's local currency. This materially improves correct invocation.

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 opens with 'Search Tes teaching jobs' and then names the exact source, Tes's tes.com teaching-jobs board. It also clarifies the tool's scope by saying it returns listing facts and a facet breakdown rather than full job descriptions, which separates it from tools like tes_job_detail.

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

Usage Guidelines4/5

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

It gives clear context on when to search: location defaults to the UK, filters are optional, and faceted labels should be sourced from a prior response. It does not explicitly name sibling alternatives or state when to choose tes_job_detail/tes_job_employer instead, so it stops short of a 5.

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

Deploy Server

Other Tools