Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tes_resource_search

Search Tes teaching resources by keyword, key stage, subject, or sale status. Retrieve listing details such as title, author, price, and rating.

Instructions

Search Tes teaching resources. Searches Tes's (tes.com) teaching-resources marketplace. Returns normalized listing facts (title, author, price, rating, downloads) -- not full listing descriptions -- out of respect for Tes's general reproduction/republication restriction. query is optional: omit it (alone, or combined with key_stage/subject/on_sale) for pure filter-driven or fully unfiltered browsing, matching Tes's own search API. 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.5/5.0
Behavior4/5

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

There are no annotations provided, so the description carries the full burden. It discloses important behavioral traits: it returns normalized listing facts, not full descriptions, due to reproduction restrictions; it mirrors Tes's own search API for unfiltered browsing; it explains that sort mirrors the Sort by dropdown and filters mirror the Refine by filters; and it clarifies that country only affects currency/localisation but not the valid key_stage/subject values. This is rich behavioral context beyond what any schema would provide.

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?

The description is a single paragraph but is densely informative with no fluff. It front-loads the main purpose and then systematically explains each parameter's role. Every sentence adds meaningful context, from return type to parameter nuances. It is appropriately concise despite covering many details.

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 search tool with 8 parameters and no output schema, the description provides sufficient guidance for an agent to correctly invoke it. It covers what is returned, how to use different parameter combos, and special notes on valid values (subject enum limitation, country scope). No critical information is missing for correct invocation.

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%, with each parameter having a description. The tool description adds value by explaining the interplay between parameters, e.g., query can be omitted for filtering, country does not affect taxonomy, and subject is not an enum list due to commas. However, it does not provide additional syntax or format details beyond what the schema already offers, so baseline 3 is appropriate.

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 clearly states the tool's purpose: 'Search Tes teaching resources' and specifies the resource (Tes.com marketplace). It also clarifies the scope and return type, distinguishing it from other dataset tools and providing concrete details like 'normalized listing facts (title, author, price, rating, downloads)'. This is a specific verb+resource that differentiates from other tool names like tes_resource_detail or tes_resource_shop.

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?

The description gives explicit guidance on when to use this tool: it is for searching the marketplace, and explains how to use the query parameter (optional, can be omitted for filter-driven browsing). It also distinguishes among sort, key_stage, subject, and country, explaining their roles and the fact that key_stage and subject are validated against a single GB taxonomy regardless of country. It does not name alternative sibling tools explicitly, but given the context of many other search endpoints, this description clearly defines the search scope and usage.

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