hemmiles-mcp-server

Search Hemmiles site

hemmiles_search_site

Read-onlyIdempotent

Search Hemmiles site content by keyword to find features, guides, blog posts, docs, pricing, and team use cases, with optional section and locale filters.

Instructions

Search hemmiles.com for pages matching a keyword query.

Because Hemmiles is a SaaS marketing site (no shopping catalog), this searches content pages — features, teams/use-cases, guides, blog posts, docs, pricing, etc. — rather than purchasable products.

Args:

query (string): keywords to match (2–100 chars).
section (string, optional): restrict to one section (e.g. 'guides', 'features').
locale (optional): market whose URLs to return (default: server locale).
deep (boolean, default true): fetch page bodies for full-text matches + snippets. Set false for a fast slug-only match.
limit (1–50, default 20), offset (default 0): pagination.
response_format ('markdown'|'json').

Returns JSON: { query, total, count, offset, has_more, next_offset?, results: [{ url, path, section, title, score, snippet }] }.

Examples:

"offline" -> finds features/offline-mode and the offline-first blog post.
"medical reps" with section='teams'.

Note: results are ranked by keyword relevance in titles, descriptions, slugs and body text; scores are relative, not absolute.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`deep`	No	If true, fetch page bodies for full-text matching and snippets (slower). If false, match slugs only.
`limit`	No	Maximum number of results to return (1–50).
`query`	Yes	Keyword(s) to search for across Hemmiles pages.
`locale`	No	Market locale/region. One of: global, in, us, gb, ca, au, nz, ie, sg, ae, za. 'global' uses the locale-less canonical pages. Defaults to the server's configured locale.
`offset`	No	Number of results to skip, for pagination.
`section`	No	Restrict search to one section.
`response_format`	No	Output format: 'markdown' (human-readable) or 'json' (structured).	markdown

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`query`	Yes
`total`	Yes
`offset`	Yes
`results`	Yes
`has_more`	Yes
`next_offset`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, but the description adds substantive behavior beyond them. It explains that deep=true fetches page bodies for full-text matching and snippets, that results are ranked by keyword relevance across titles, descriptions, slugs, and body text, and that scores are relative rather than absolute.

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?

The description is front-loaded with the core purpose and then organized into Args, Returns, Examples, and Note sections. It is appropriately detailed for a seven-parameter search tool, though the return-shape description and per-parameter recaps partly duplicate the schema/output schema.

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?

Given the moderate complexity, rich annotations, 100% schema description coverage, and presence of an output schema, the description is complete enough for an agent to select and invoke the tool correctly. It covers purpose, parameter behavior, examples, pagination, ranking semantics, and return format.

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 description coverage is 100%, so the schema already documents all seven parameters. The description still adds useful meaning, especially that locale controls which market's URLs are returned, that deep=false performs a fast slug-only match, and that section can restrict results to areas like 'guides' or 'features'.

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 states a specific verb and resource: 'Search hemmiles.com for pages matching a keyword query.' It also distinguishes the tool from catalog/product search by explaining that Hemmiles is a SaaS marketing site and this searches content pages such as features, guides, blog posts, docs, and pricing.

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?

Usage is clear from the keyword-search framing, the deep=false fast slug-only option, and examples like '"offline"' and '"medical reps" with section="teams"'. It does not explicitly compare against siblings such as list_pages or get_page, but the intended search use case is understandable.

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

Deploy Server