PageHub

Search blocks

search_blocks

Read-onlyIdempotent

Search the block library; returns one page of slugs with descriptions and tags (Liquid: get_block). Blocks are copy-source examples, not defaults. q takes short layout phrases ("split hero"), categories / styles arrays OR-filter, page pages through. Guide: get_style_reference({ topic: "blocks" }).

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": "search_blocks"
  }
}

Input Schema

Name	Required	Description
`q`	No	Short layout phrase, e.g. "photo hero"; sorts by relevance.
`id`	No	Site id.
`tag`	No	e.g. "pricing".
`page`	No	Default 1.
`sort`	No	popular \| newest \| name \| relevance. Default: relevance with q, else newest.
`group`	No	Logical group, e.g. "acme-homepage-cards".
`limit`	No	Default 50, max 100.
`style`	No	One vibe; auto-set from the site's buildStyle.
`preset`	No	Starter/bundle id, e.g. "acme".
`source`	No	Legacy field; prefer preset.
`styles`	No	OR-filter by several vibes.
`category`	No	One category (merged with categories).
`featured`	No	Curated only.
`blockType`	No	section (default) = page sections; component = patterns inside sections.
`categories`	No	OR-filter by several categories.
`subcategory`	No	e.g. "testimonials".

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 25, 2026

addedInput schema / properties / id

Added value: +{
+  "description": "Site id.",
+  "maxLength": 256,
+  "type": "string"
+}

First observedSep 28, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world, so the safety profile is settled. The description contributes non-obvious behavior: results are paginated to one page and items are copy-source examples rather than defaults. It doesn't mention result caps or empty-result behavior, keeping it below a 5.

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 purpose and return shape, then the usage caveat, then parameter hints. It is dense and earns its space, though the terse backtick style and compressed clauses make it slightly harder to parse than plain prose.

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 16-parameter, no-output-schema search tool, the description supplies what the schema cannot: the page-based return shape, the copy-source semantics, and the OR-filter/paging behavior. Combined with annotations and full schema coverage, an agent has everything needed to call it correctly.

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 description coverage is 100%, so every one of the 16 parameters is already documented, including q, categories, styles, and page. The description restates that q takes short layout phrases, that the arrays OR-filter, and that page pages through — useful reinforcement but nearly duplicative of the schema, so baseline 3 applies.

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 ("Search the block library") and immediately defines the return shape ("one page of slugs with descriptions and tags"). The parenthetical Liquid equivalent and the pointer to get_block separate it from list_blocks and get_block 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 Guidelines4/5

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

Adds a real decision rule that isn't anywhere else: "Blocks are copy-source examples, not defaults" tells the agent these are starting points to copy, not drop-in defaults. It routes to get_style_reference for deeper guidance, but never explicitly contrasts with sibling list_blocks, so it stops short of a full when/when-not.

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

All PageHub 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.

Resources

Need Help?