Skip to main content
Glama
chrischall

onehome-mcp

by chrischall

Bulk-fetch OneHome listings by id

onehome_bulk_get
Read-onlyIdempotent

Retrieve up to 200 OneHome property listings in a single request. Each input ID returns a row with property details or an error, ensuring partial failures don't block the entire batch.

Instructions

Fetch up to 200 OneHome listings in a single call. Returns one structured row per input id (no side-by-side summary table — use onehome_compare_properties for that). Each row is either { listing_id, property } on success or { listing_id, error } on failure — one bad id never fails the whole call. Calls fan out concurrently against ListingById, capped at 6 in flight to avoid swamping the bridge; transient bridge timeouts are retried once per row before being captured as an error. extracted_features is populated per row automatically. The raw description (PublicRemarks) is omitted by default — pass include_description: true to keep it. group_id defaults to the magic-link session context.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_idNo
listing_idsYesListing OSK ids to fetch. 1..200. For higher counts, batch into multiple calls.
saved_search_idNo
include_descriptionNoInclude the raw `description` (PublicRemarks) on each row. Defaults to `false`.
Behavior5/5

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

Adds significant behavioral details beyond annotations: concurrent fan-out with cap of 6, retry policy for timeouts, per-row error handling, default omission of `description`, and default `group_id` from session. No contradictions with readOnlyHint/idempotentHint.

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?

Front-loaded with main purpose, each sentence adds value. Slightly verbose in detailing concurrency and retry, but all information is relevant.

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?

Explains return format (rows with success/error), concurrency limits, and default behavior. No output schema, but description provides sufficient detail. Missing specifics on `saved_search_id` and `group_id` fallback, but overall complete for core functionality.

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?

Adds context for `listing_ids` (batch size constraint reiterated), explains `include_description` default and effect, and `group_id` default behavior. Schema coverage is 50% but description compensates for some gaps. `saved_search_id` lacks extra clarification.

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?

Describes specific verb+resource (fetch listings by id), distinguishes from sibling `onehome_compare_properties` by clarifying it returns rows per id instead of a side-by-side summary.

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?

Explicitly contrasts with `onehome_compare_properties` for side-by-side needs, and advises batching for more than 200 ids. No explicit exclusion of other alternatives, but context is clear.

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/chrischall/onehome-mcp'

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