searchts

Overview Schema Source Related Servers Score Discussions Admin

grab_site

Fetch a web page and download its design assets—images, icons, CSS, fonts, SVG—extract the color palette and fonts in use, and return a manifest with local file paths.

Instructions

Grab a page for design inspiration: fetch it through the unlock ladder, download its assets (images/icons/css/fonts/svg), extract the color palette and the fonts in use, and return a manifest (with local file paths) as JSON. Use this for a whole page's design/assets at once; for a single known file use fetch_asset. Saves into out_dir when given, otherwise a 'searchts-grab-' folder. Set read=true to also save the page text as page.md. Returns an 'Error: ...' string on failure.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`read`	No
`out_dir`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv0.8.0Aug 29, 2026

addedInput schema / properties / out_dir / default
```
Added value: +""
```

removedInput schema / properties / out_dir / description

Removed value: -"Directory to save into (optional; defaults to 'searchts-grab-<host>')."

addedInput schema / properties / out_dir / title
```
Added value: +"Out Dir"
```
addedInput schema / properties / read / default
```
Added value: +false
```

removedInput schema / properties / read / description

Removed value: -"If true, also save the page text as page.md (default false)."

addedInput schema / properties / read / title
```
Added value: +"Read"
```
removedInput schema / properties / url / description
```
Removed value: -"URL of the page to grab."
```
addedInput schema / properties / url / title
```
Added value: +"Url"
```
addedInput schema / title
```
Added value: +"grab_site_toolArguments"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "grab_site_toolOutput",
+  "type": "object"
+}

First observedv0.5.1Jul 6, 2026

TDQS

A5/5.0

Behavior5/5

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

With no annotations, the description carries full behavioral burden. It discloses the fetch mechanism, the disk-saving behavior (out_dir or default folder), the optional page.md side effect, and the 'Error: ...' failure return. This is strong transparency for a download/capture operation.

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 compact yet complete: it front-loads the core purpose, then gives routing guidance, parameter behavior, and error handling. Every sentence earns its place, with no repetition of schema defaults or annotations.

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 multi-step tool with no annotations and no schema parameter descriptions, this description covers what, when, how, parameter side effects, save location, and failure mode. The output schema handles the manifest structure, so the prose does not need to enumerate return fields.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate. It explains read=true (saves page text as page.md), out_dir semantics including the default 'searchts-grab-<host>' folder, and the url parameter is self-evident from 'Grab a page'. An agent can set all three parameters correctly from this text.

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 names the resource (a page), the specific actions (fetch through the unlock ladder, download assets, extract palette/fonts, return a manifest JSON), and explicitly contrasts with fetch_asset for single files. The phrase 'a whole page's design/assets at once' clearly anchors its scope and differentiates it from siblings.

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?

It gives explicit when-to-use guidance ('Use this for a whole page's design/assets at once') and an explicit alternative for a different case ('for a single known file use fetch_asset'). The read flag condition is also explained, so an agent can decide correctly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server