Skip to main content
Glama
CryptoCultCurt

Appfolio MCP Server

get_unit_vacancy_detail_report

Generate a detailed unit vacancy report. Filter by property, group, portfolio, or owner using numeric IDs, and select columns like rent, status, and amenities.

Instructions

Generates a report on unit vacancies. IMPORTANT: All ID parameters (owners_ids, properties_ids, etc.) must be numeric strings (e.g. '123'), NOT names. Use respective directory reports first to lookup IDs by name if needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
propertiesNoFilter results based on properties, groups, portfolios, or owners. All ID fields must be numeric strings, not names.
property_visibilityNoFilter units by status. Defaults to "active"active
tagsNoOptional. Filter by a comma-separated list of tags (e.g., "bbq,deck").
columnsNoArray of specific columns to include in the report. Valid columns: advertised_rent, posted_to_website, posted_to_internet, property, property_name, amenities, lockbox_enabled, affordable_program, address, street, street2, city, state, zip, unit, unit_tags, unit_type, bed_and_bath, sqft, unit_status, rent_ready, days_vacant, last_rent, schd_rent, new_rent, last_move_in, last_move_out, available_on, next_move_in, description, amenities_price, computed_market_rent, ready_for_showing_on, unit_turn_target_date, advertised_rent_months, property_id, unit_id. If not specified, all columns are returned.
Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It only states the purpose and parameter requirements, but does not mention read-only nature, side effects, authentication needs, or rate limits.

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 a single sentence with a highlighted important note. It is concise, front-loaded, and contains no redundant information.

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

Completeness2/5

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

Given the absence of an output schema and the complexity of parameters, the description fails to explain what the report returns or any expected output structure. This leaves agents with incomplete information.

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 already includes ID format hints. The description reinforces this but adds little new meaning beyond the schema. Baseline score of 3 is appropriate.

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 the tool generates a report on unit vacancies. It also includes an important clarification about ID format, distinguishing it from other report tools.

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?

The description explicitly instructs users to use numeric strings for IDs and to lookup IDs using directory reports first. This provides clear when-to-use guidance, though it does not explicitly contrast with sibling report tools.

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/CryptoCultCurt/appfolio-mcp-server'

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