Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tes_resource_shop

Get a Tes teaching-resources author shop by username to see profile stats, bio, and paginated resource listings; filter listings by subject.

Instructions

Get a Tes teaching-resources author shop. Returns detail for one teaching-resources author/seller shop by its username (from tes-resource-search/tes-resource-detail's author field, or the trailing path segment of author_url): display name, average rating, upload/view/download counts, a bio, and a page of that author's resource listing (id, title, price, thumbnail -- call tes-resource-detail with each id for subject/age-range/resource-type/rating/description). subject narrows the listing to one of the subject tabs shown on the shop's own page; these vary per author and are not a curated enum.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoOne-based page
subjectNoSubject tab to filter the listing to -- see the shop's own page for the current set
usernameYesTes author username

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 full burden and does well: it enumerates the returned shop fields (display name, rating, upload/view/download counts, bio) and the shape of the embedded listing (id, title, price, thumbnail). It omits pagination behavior at the boundaries, but the disclosure is otherwise strong.

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-loads the core purpose, then layers sourcing and return details. It is information-dense but every clause serves a routing or output purpose, with only mild verbosity in the returned-field enumeration.

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?

No output schema exists, so the description must describe returns, and it does so thoroughly, including how to further resolve listing items via tes-resource-detail. Nothing essential for correct invocation 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% so baseline is 3, but the description adds real meaning by explaining the username source and clarifying that subject is not a fixed enum but varies per author. page is left to the schema.

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 ('Get a Tes teaching-resources author shop') and immediately scopes it to a single author/seller by username. It is clearly distinguishable from the sibling tes_resource_search and tes_resource_detail tools it references.

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?

Explains exactly where the required username comes from (the author field of tes-resource-search/tes-resource-detail, or the trailing segment of author_url) and points at tes-resource-detail for the per-resource follow-up. It gives clear context but no explicit when-not or exclusion statement.

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