Skip to main content
Glama
tonywang0122

買屋快搜

by tonywang0122

house_search

Search Taiwan housing listings by city, district, room count, price, and age to find matching properties with pricing and details.

Instructions

搜尋房屋物件列表。

回傳結構:

  • total / page / page_size / page_count:分頁資訊

  • newin_cnt / newprice_cnt / hot_cnt / hot_deal_cnt / bestprice_cnt:各類統計數

  • items[]:物件列表,每筆包含 id、名稱、地址、座標、總價、單價、原始開價、 降價幅度、格局、加蓋格局、樓層、屋齡、建物/主建物/土地面積、車位、 陽台/景觀/影片/3DVR 旗標、首圖/大圖 URL、標籤、關注人數、社區、分享連結等

Args: city: 城市代碼。Taipei=台北市, NewTaipei=新北市, Taoyuan=桃園市, Hsinchu=新竹市, Taichung=台中市, Tainan=台南市, Kaohsiung=高雄市, Keelung=基隆市, Miaoli=苗栗縣, Changhua=彰化縣, Nantou=南投縣, Yunlin=雲林縣, Chiayi=嘉義市, Pingtung=屏東縣, Yilan=宜蘭縣, Hualien=花蓮縣, Taitung=台東縣 zip: 行政區 zipCode,多個逗號分隔。 台北市: 100=中正,103=大同,104=中山,105=松山,106=大安,108=萬華, 110=信義,111=士林,112=北投,114=內湖,115=南港,116=文山。 新北市: 220=板橋,221=汐止,231=新店,234=永和,235=中和,236=土城, 241=三重,242=新莊,244=林口,247=蘆洲,251=淡水 type: 物件類型,多個逗號分隔。apartment=公寓, building=電梯大樓(B), dalou=大樓(L), huaxia=華廈(M), flat=套房, villa=別墅/透天, store=店面, office=辦公, land=土地 rooms: 房數。3=正好3房, 2-3=2~3房, 4+=4房以上, 2-=2房以下 price: 總價(萬元)。1500-3000=區間, 2000+=以上, 1000-=以下 area: 建物坪數。20-40=區間, 50+=以上, 15-=以下 year: 屋齡(年)。0-10=區間, 30+=以上, 5-=以下 floor: 樓層。2-5=區間, 10+=以上, 3-=以下 tags: 標籤ID逗號分隔。4=有陽台,5=廁所開窗,7=有裝潢,6=有景觀, 102=有電梯,17=近捷運,19=近學校,18=近市場,16=近公園, 12=警衛管理,13=新上架,106=新降價 exclude: 排除條件。4f=排除4樓, sfroofplus=排除頂加, sfdarkroom=排除暗房, sfside=排除邊間 keyword: 關鍵字搜尋(物件名稱),如:面寬邊間、河景 sort: 排序。price-asc=價格低到高, price-desc=高到低, publish-desc=最新上架, diff-desc=降價幅度 status: presale=預售屋, resale=成屋 page: 頁次(預設1) page_size: 每頁筆數(預設20)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zipNo
areaNo
cityYes
pageNo
sortNo
tagsNo
typeNo
yearNo
floorNo
priceNo
roomsNo
statusNo
excludeNo
keywordNo
page_sizeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains the return structure (pagination, statistics, item fields) and parameter filtering behavior, which is transparent about what the tool returns. It does not mention rate limits or authentication, but for a search tool, the read-only nature is clear.

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 front-loaded with a one-line purpose, followed by a structured return format summary and a parameter list. Despite its length, every sentence adds necessary detail, with no wasted words. The clear sections and parameter enumeration make it appropriately sized for a tool with 15 parameters.

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 tool's complexity (15 parameters, varied filter options, output schema), the description is exceptionally complete. It covers all parameters with examples, describes return structures, and provides sufficient context for an agent to call the tool correctly without additional information. The presence of an output schema is leveraged, while the description adds essential parameter details.

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%, and the description compensates by providing exhaustive semantics for all 15 parameters. Each parameter includes allowed values, examples, and context (e.g., city codes, zip mappings, type definitions). This goes well beyond the minimal schema titles and defaults, giving the agent complete guidance for correct invocation.

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 '搜尋房屋物件列表' (search house object list), which is a specific verb (search) and resource (house object list). It distinguishes itself from the sibling tool house_get_detail by focusing on list retrieval with filters, making its purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description provides extensive filter details, implying it is used for searching and filtering house listings. However, it does not explicitly mention when to use this tool versus house_get_detail, nor does it state exclusion criteria. Usage is implied rather than explicitly guided.

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

Install Server

Other Tools

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/tonywang0122/house-search-mcp'

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