Crawlora MCP

tes_resource_search

Read-only

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. Use tes_resource_detail to get a Tes teaching resource.

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_resource_search"
  }
}

Input Schema

Name	Required	Description
`page`	No	One-based page
`sort`	No	Sort order. Documented values: relevance, newest, highest_rated, lowest_price.
`query`	No	Search keywords -- omit for filter-driven or unfiltered browsing
`country`	No	Storefront market. Documented values: GB, US, AU, IE, CA, NZ, UN.
`on_sale`	No	Filter to discounted resources only
`subject`	No	Filter 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). Documented values: .
`key_stage`	No	Filter by age range. Documented values: 3-5, 5-7, 7-11, 11-14, 14-16, 16+, age_not_applicable.
`page_size`	No	Results per page

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.

Changed8 schema fields changedOct 7, 2026

addedInput schema / properties / country / description

Added value: +"Storefront market. Documented values: GB, US, AU, IE, CA, NZ, UN."

addedInput schema / properties / key_stage / description

Added value: +"Filter by age range. Documented values: 3-5, 5-7, 7-11, 11-14, 14-16, 16+, age_not_applicable."

addedInput schema / properties / on_sale / description

Added value: +"Filter to discounted resources only"

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

addedInput schema / properties / query / description

Added value: +"Search keywords -- omit for filter-driven or unfiltered browsing"

addedInput schema / properties / sort / description

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

addedInput schema / properties / subject / description

Added value: +"Filter 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). Documented values: ."

First observedOct 7, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds rich context beyond that: what the results contain (normalized listing facts, not full descriptions, and the reproduction-restriction reason why), how query omission behaves, and that country only affects currency/localisation. This is real behavioral disclosure.

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?

Front-loaded with the purpose sentence, then the return-value and parameter behavior in a dense but single block. Every clause carries information, though the run-on structure and mid-sentence parentheticals reduce readability slightly.

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 an 8-parameter filter/search tool with an output schema and full annotation coverage, the description covers purpose, return shape, parameter semantics, and sibling routing. Combined with the existing output schema, nothing an agent needs to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, but the description adds meaning beyond the schema: it maps sort to the real Sort by dropdown, key_stage/subject to the Refine by facet taxonomy, notes subject has 29 comma-containing values so see the endpoint markdown, and clarifies country does not change which key_stage/subject values are valid. Only mild gap is that it defers the subject list elsewhere.

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 specific verb+resource ('Searches Tes's (tes.com) teaching-resources marketplace') and immediately distinguishes itself from the sibling tes_resource_detail, which it names explicitly. An agent can tell what this tool returns and how it differs from the detail tool without opening either schema.

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?

Gives explicit when-to-use guidance: query is optional, omit it (alone or with filters) for filter-driven or unfiltered browsing, and it mirrors Tes's own search API. It also routes to tes_resource_detail for full resource details. Nothing is left to inference.

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.