Skip to main content
Glama
CryptoCultCurt

Appfolio MCP Server

get_rent_roll_itemized_report

Fetches a detailed, itemized rent roll report filtered by properties, unit status, tags, GL accounts, date, and selected columns.

Instructions

Returns rent roll itemized report for the given filters. IMPORTANT: All ID parameters (properties_ids, property_groups_ids, portfolios_ids, owners_ids, gl_account_ids) must be numeric strings (e.g. '123'), NOT names. CRITICAL: gl_account_ids are internal database IDs, NOT GL account numbers! Do not use GL account numbers like '4630', '4635' - use the Chart of Accounts Report first to lookup the correct gl_account_ids.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
propertiesNo
unit_visibilityNoFilter units by status. Defaults to "active".active
tagsNoTags filter
gl_account_idsNoArray of GL account IDs (internal database IDs, NOT GL account numbers). These are numeric strings like "123", "456". Do NOT use GL account numbers like "4630", "4635". Use the Chart of Accounts Report to lookup gl_account_ids by GL account number or name.
as_of_dateYesReport date in YYYY-MM-DD format
columnsNoArray of specific columns to include in the report. Valid columns: property, property_name, property_id, property_address, property_street, property_street2, property_city, property_state, property_zip, property_type, occupancy_id, unit_id, unit, unit_tags, unit_type, bd_ba, tenant, status, sqft, market_rent, computed_market_rent, advertised_rent, total, other_charges, monthly_rent_square_ft, annual_rent_square_ft, deposit, lease_from, lease_to, last_rent_increase, next_rent_adjustment, next_rent_increase_amount, next_rent_increase, move_in, move_out, past_due, nsf, late, amenities, additional_tenants, monthly_charges, rent_ready, rent_status, legal_rent, preferential_rent, tenant_tags, tenant_agent, property_group_id, portfolio_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 provided, so description carries full burden. It only states it returns a report, but doesn't disclose behavioral traits like read-only nature, output format, or error handling. For a mutation tool this would be insufficient, but for a report tool the lack is still noticeable.

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?

Extremely concise: two sentences that front-load the purpose and provide critical warnings. No unnecessary words. Every sentence adds value.

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 no output schema, description should describe what the report returns (e.g., list of items with columns). It only says 'itemized report' without details. Lacks information on output structure, pagination, or error scenarios. Incomplete for a tool with 6 parameters.

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 high (83%), so baseline is 3. Description repeats the ID format warnings which are critical but already in schema. It adds emphasis but little new meaning. Does not explain parameter relationships or context beyond 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?

Description clearly states it returns a rent roll itemized report with filters. While it doesn't explicitly differentiate from sibling report tools, the name and description are specific enough to identify its purpose.

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 critical usage guidance: ID parameters must be numeric strings and gl_account_ids are internal IDs, not account numbers. Suggests using Chart of Accounts Report for lookup. However, it doesn't specify when to use this tool vs alternative reports.

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