Skip to main content
Glama
CryptoCultCurt

Appfolio MCP Server

get_property_directory_report

Get a property directory report with details like status, address, units, and owner info. Filter results via numeric IDs for properties, groups, portfolios, or owners.

Instructions

Retrieves a property directory report with details about properties, including status, address, units count, and owner information. IMPORTANT: All ID parameters (owners_ids, properties_ids, etc.) must be numeric strings (e.g. '123'), NOT names. Use Owner Directory Report first to lookup owner IDs by name if needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
property_visibilityNoFilter properties by status. Defaults to "active"active
propertiesNoFilter results based on property, group, portfolio, or owner IDs. All values must be numeric ID strings, not names.
columnsNoArray of specific columns to include in the report. Valid columns: property, property_name, property_id, property_integration_id, property_address, property_street, property_street2, property_city, property_state, property_zip, property_county, market_rent, units, sqft, management_flat_fee, management_fee_percent, minimum_fee, maximum_fee, waive_fees_when_vacant, reserve, home_warranty_expiration, insurance_expiration, tax_year_end, tax_authority, owners_phone_number, payer_name, description, portfolio, premium_leads_status, premium_leads_monthly_cap, premium_leads_activation_date, owner_i_ds, property_group_id, portfolio_id, portfolio_uuid, visibility, maintenance_limit, maintenance_notes, site_manager_name, site_manager_phone_number, management_fee_type, lease_fee_type, lease_flat_fee, lease_fee_percent, renewal_fee_type, renewal_flat_fee, renewal_fee_percent, future_management_fee_start_date, future_management_fee_percent, future_management_flat_fee, future_minimum_fee, future_maximum_fee, future_management_fee_type, future_waive_fees_when_vacant, owner_payment_type, property_type, property_created_on, property_created_by, owners, prepayment_type, late_fee_type, late_fee_base_amount, late_fee_daily_amount, late_fee_grace_period, late_fee_grace_period_fixed_day, late_fee_grace_balance, max_daily_late_fees_amount, ignore_partial_payments, admin_fee_amount, year_built, contract_expirations, management_start_date, management_end_date, management_end_reason, agent_of_record, tax_region_code, property_class, online_maintenance_request_instructions, amenities, listing_type. 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 fully convey behavioral traits. It implies a read operation (retrieves a report) but does not confirm read-only nature, disclose auth requirements, rate limits, or potential side effects. The description focuses on content rather than behavior.

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 concise sentences: one stating the purpose, and one providing critical usage guidance. No filler words. The important note is front-loaded with 'IMPORTANT' for emphasis.

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 report tool with no output schema, the description covers the purpose and critical parameter constraints. It is missing default behavior (e.g., returns all properties if no IDs specified) and pagination info, but these are common defaults. Overall sufficient for an agent to use correctly.

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 coverage is 100%, so the schema already describes all parameters. The description reiterates the numeric string requirement and cross-references another tool, adding marginal value beyond schema. However, it does not elaborate on the properties object structure or columns selection beyond what's in the schema.

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 verb 'Retrieves' and the specific resource 'property directory report', listing included details (status, address, units count, owner information). This distinguishes it from sibling tools like get_owner_directory_report or get_unit_directory_report.

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?

Provides explicit guidance on parameter usage: all ID parameters must be numeric strings, not names, and directs to use Owner Directory Report for name-to-ID lookup. Does not explicitly contrast with other property-related reports, but the instruction is actionable.

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