buildium-mcp

Buildium List Rentals

buildium_list_rentals

Read-onlyIdempotent

List rental properties from Buildium by selecting fields, counting records, or fetching all pages for totals.

Instructions

List rental properties. Pass fields to narrow large records.

To count, use count_only; for totals, all_pages.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Records per page, 1-1000.
`fields`	No	Keep only these top-level fields in each record, e.g. ["Id", "Name"]. Buildium records are large and carry tax IDs and addresses you may not need.
`offset`	No	How many records to skip. Use next_offset from the previous page.
`all_pages`	No	Follow pagination and return the records, up to 1000. Use it for totals and other aggregates; a figure from one page is wrong whenever there is more than one page.
`count_only`	No	Follow every page, up to 100,000 records, and return only how many there are. Use it for "how many" questions.
`exclude_fixtures`	No	Leave out test records, whose names start with the fixture prefix (see buildium_health). When any are present the response says so either way.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.2.1Sep 24, 2026

addedInput schema / properties / all_pages / description

Added value: +"Follow pagination and return the records, up to 1000. Use it for totals and other aggregates; a figure from one page is wrong whenever there is more than one page."

addedInput schema / properties / count_only / description

Added value: +"Follow every page, up to 100,000 records, and return only how many there are. Use it for \"how many\" questions."

addedInput schema / properties / exclude_fixtures / description

Added value: +"Leave out test records, whose names start with the fixture prefix (see buildium_health). When any are present the response says so either way."

addedInput schema / properties / fields / description

Added value: +"Keep only these top-level fields in each record, e.g. [\"Id\", \"Name\"]. Buildium records are large and carry tax IDs and addresses you may not need."

addedInput schema / properties / limit / description
```
Added value: +"Records per page, 1-1000."
```

addedInput schema / properties / offset / description

Added value: +"How many records to skip. Use next_offset from the previous page."

Changed1 schema field changedv0.2.0Sep 23, 2026
- addedInput schema / properties / count_only
```
Added value: +{
+  "default": false,
+  "type": "boolean"
+}
```
First observedv0.1.0Sep 17, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds a minor behavioral note about narrowing large records via fields, which is useful but not substantial; it doesn't contradict 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 two short lines with zero fluff. The main purpose is front-loaded, and the additional guidance on count_only/all_pages is relevant. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 6 parameters and an output schema, so much is already structured. The description is adequate for a simple list operation but lacks sibling routing and any mention of the response structure or when pagination is implicitly required. It's not misleading, but an agent could benefit from knowing how this relates to other list tools.

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%, and each parameter already has a detailed description explaining its purpose and usage (e.g., offset explains next_offset, all_pages warns about page-figure inaccuracies). The description's one-line tip about fields adds negligible value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'List rental properties', a clear verb+resource that identifies the tool's function. It differentiates from siblings like buildium_list_units and buildium_list_leases by naming 'rental properties', though it doesn't explicitly call out alternatives as the best examples do.

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

Usage Guidelines2/5

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

The description only gives parameter-level guidance ('To count, use count_only; for totals, all_pages') and doesn't explain when to prefer this tool over siblings such as buildium_get_rental or buildium_list_units. There is no mention of context, prerequisites, or exclusion conditions.

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