Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tes_resource_search

Search Tes teaching resources and filter by keywords, subject, key stage, sale status, country, and sort order; returns listing facts such as title, author, price, rating, and downloads.

Instructions

Search Tes teaching resources. Searches Tes's (tes.com) teaching-resources marketplace. Returns listing facts (title, author, price, rating, downloads) -- not full listing descriptions. query is optional: omit it (alone, or combined with key_stage/subject/on_sale) for pure filter-driven or fully unfiltered browsing. sort mirrors the real search page's own Sort by dropdown; key_stage and subject mirror its left-hand Refine by filters (both closed, validated enums taken from Tes's own facet taxonomy, and always resolved against Tes's own single GB-taxonomy regardless of country). country controls result currency/localisation only (confirmed live for all seven values); it does not change which key_stage/subject values are valid.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoOne-based page
sortNoSort order
queryNoSearch keywords -- omit for filter-driven or unfiltered browsing
countryNoStorefront market
on_saleNoFilter to discounted resources only
subjectNoFilter by subject -- one of Tes's own top-level subject facet labels; see the endpoint markdown for the full list (two of the 29 values contain a comma, which is why this parameter is not expressed as a Swagger Enums() list)
key_stageNoFilter by age range
page_sizeNoResults per page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.17.5
    • addedInput schema / properties / country / enum
      Added value: +[
+  "GB",
+  "US",
+  "AU",
+  "IE",
+  "CA",
+  "NZ",
+  "UN"
+]
    • addedInput schema / properties / key_stage / enum
      Added value: +[
+  "3-5",
+  "5-7",
+  "7-11",
+  "11-14",
+  "14-16",
+  "16+",
+  "age_not_applicable"
+]
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "relevance",
+  "newest",
+  "highest_rated",
+  "lowest_price"
+]
    • addedInput schema / properties / subject / enum
      Added value: +[
+  ""
+]
  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 burden and does well: it discloses the exact return fields (title, author, price, rating, downloads), warns that full listing descriptions are not returned, and clarifies that country only affects currency/localisation and not taxonomy validity. It omits any mention of auth requirements, rate limits, or pagination behavior.

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?

Purpose is front-loaded and every sentence carries information, but the opening is slightly redundant ('Search Tes teaching resources. Searches Tes's ... marketplace') and the nested parentheticals make it dense. It is appropriately sized for an 8-parameter tool.

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 tool with no output schema and 8 zero-required parameters, it explains return content, filter semantics, and the country/taxonomy interaction well. It does not describe pagination behaviour despite page and page_size parameters, a minor gap given the schema already documents them.

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?

Schema coverage is 100% (baseline 3), yet the description adds real meaning beyond it: query's optionality semantics, that sort mirrors the site's Sort-by dropdown, that key_stage/subject are validated enums from Tes's own facet taxonomy resolved against a single GB taxonomy regardless of country, and that country changes currency but not taxonomy. This resolves genuine ambiguity the schema alone leaves open.

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?

States a precise verb ('Search') and resource ('Tes teaching resources' on the tes.com marketplace), and the note that it returns listing facts rather than full descriptions implicitly routes the agent away from tes_resource_detail. The scope (which marketplace, what kind of result) is unambiguous.

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?

Gives explicit conditional guidance for the optional query ('omit it alone or combined with key_stage/subject/on_sale for pure filter-driven or fully unfiltered browsing') and ties sort/key_stage/subject to the real search page's controls. It does not name alternative tools such as tes_resource_detail or tes_resource_shop, so the routing guidance is strong on parameters but silent on sibling selection.

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