Crawlora MCP

tiffany_content_search

Read-only

Search Tiffany & Co.'s own editorial pages -- style guides, gift guides, and other World of Tiffany articles -- by free-text keyword. Not product data. A genuine non-matching keyword returns a well-formed empty result.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keyword": "<keyword>"
    },
    "name": "tiffany_content_search"
  }
}

Input Schema

Name	Required	Description
`page`	No	One-based page
`keyword`	Yes	Search keyword
`per_page`	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.

Changed3 schema fields changedOct 7, 2026
- addedInput schema / properties / keyword / description
```
Added value: +"Search keyword"
```
- addedInput schema / properties / page / description
```
Added value: +"One-based page"
```
- addedInput schema / properties / per_page / description
```
Added value: +"Results per page"
```
First observedOct 7, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it discloses the free-text matching nature and that a non-matching keyword yields a well-formed empty result, telling the agent an empty set is legitimate rather than an error.

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?

Three tight sentences, front-loaded with the core scope and followed by the differentiator and the empty-result caveat. No redundant filler, though the final sentence is slightly tangential to selection.

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?

An output schema exists, so return-value detail is unnecessary, and the description covers purpose, scope boundary, and empty-result behavior. Combined with annotations it is nearly complete for a three-param search tool.

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 page, keyword, and per_page are already documented in the schema. The description only restates 'free-text keyword' and adds no syntax, format, or pagination semantics beyond the schema, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb (search) plus resource (Tiffany's own editorial pages: style guides, gift guides, World of Tiffany articles) with concrete examples. 'Not product data' clearly separates it from the tiffany_search/tiffany_product siblings, though it does not name the alternative tool directly.

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?

Establishes when to use it (free-text keyword search over editorial content) and gives an exclusion ('Not product data'), implicitly steering agents toward product tools for merchandise. It does not explicitly name the sibling to use instead, so it falls short of a full 5.

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.