Skip to main content
Glama
TKMD
by TKMD

search.facets

Read-onlyIdempotent

Classify search results by sectionType, industry, audience, and tags, returning counts per value for building filter selection interfaces.

Instructions

[DEPRECATED: Use search.unified with include_facets: true instead] ファセット検索(絞り込みカウント表示)。検索結果をsectionType・industry・audience・tagsで分類し、各値の件数を返却します。検索結果の絞り込みUIやフィルタ選択に使用します。代替: search.unified({ query: '...', include_facets: true, facet_fields: ['sectionType'], enable_reranking: false, limit: 50 }) / Faceted search with filter counts. Classifies search results by sectionType, industry, audience, and tags, returning counts per value. Used for search result refinement UI and filter selection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoタグフィルター / Tags filter
limitNoファセット算出のベース結果数(1-50、デフォルト: 50) / Base result limit for facet computation (1-50, default: 50)
queryYes検索クエリ(自然言語、1-500文字) / Search query (natural language, 1-500 chars)
audienceNoターゲットオーディエンスフィルター / Target audience filter (e.g., 'Developer')
industryNo業種フィルター / Industry filter (e.g., 'SaaS', 'E-commerce')
webPageIdNoWebページIDでフィルター / Filter by web page ID
facet_fieldsNoファセットフィールド(デフォルト: 全フィールド) / Facet fields (default: all). sectionType: セクション/パーツタイプ, industry: 業種, audience: ターゲット, tags: タグ

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Addedv0.3.0

TDQS

A4.4/5.0
Behavior4/5

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

Beyond annotations (readOnlyHint, idempotentHint), the description adds that the tool performs faceted search returning counts, and lists the specific facet fields. It also discloses the deprecation status, which is important behavioral information not captured by annotations.

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 very concise, with two sentences in each language. The deprecation notice is front-loaded, and every sentence serves a clear purpose (deprecation, functionality, use case, migration path). No unnecessary words.

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?

For a deprecated tool with full schema coverage and annotations, the description adequately covers purpose, usage, and migration. It does not specify return format (no output schema), but that is acceptable given the deprecation and the alternative provided.

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 the schema already documents parameters well. The description does not add significant semantic value beyond listing the four facet fields, which are also in the schema. Baseline is 3, and there is no substantial improvement.

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 clearly states it is a faceted search that returns counts for specific fields (sectionType, industry, audience, tags) and is used for UI refinement. It also distinguishes itself from the deprecated status and directs to search.unified, a sibling tool.

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?

The description explicitly marks the tool as deprecated and provides the exact alternative call using search.unified with include_facets and relevant parameters. It also describes typical use cases (filter selection), giving clear guidance on when to use this tool versus alternatives.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TKMD/ReftrixMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server