Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

thebodyshop_page

Get a The Body Shop static page by handle to return cleaned text, title, URL, and timestamps; invalid handles return 404.

Instructions

Get a The Body Shop static page. Returns one The Body Shop static page by its handle: id, title, URL, plain-text content and the created, published and updated timestamps. Page text is cleaned, not raw HTML. An unknown handle returns 404. When the reduced form is served, transport_mode is ssr_embedded and id is omitted.

Input Schema

NameRequiredDescriptionDefault
handleYesPage handle

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A3.9/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 delivers real behavioral context beyond the schema: 404 on unknown handle, cleaned plain-text rather than raw HTML, and the reduced-form behavior where transport_mode is ssr_embedded and id is omitted. It does not cover auth or rate limits, but the disclosed behaviors are substantive.

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 what the tool does and its return shape, then adds edge cases (404, reduced form) as trailing sentences. Every sentence carries information, though the enumeration of return fields is slightly list-like.

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?

No output schema exists, so the description sensibly enumerates the returned fields (id, title, URL, content, timestamps) and covers the error and reduced-form cases. Complete enough for an agent to call it correctly, with only auth/permission context absent.

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 coverage is 100%, so the single handle parameter is already documented. The description only restates that lookup is by handle, adding no format or example detail beyond the schema, which matches the baseline 3.

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 and resource ('Get a The Body Shop static page') and immediately narrows scope to a single page fetched by its handle. This distinguishes it from the sibling thebodyshop_pages list tool without needing the schema.

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

Usage Guidelines3/5

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

Usage is implied: it returns one page by handle, which suggests use when you already know the handle. However, no alternative (such as thebodyshop_pages for listing) is named, and there is no explicit when/when-not guidance.

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