Skip to main content
Glama
CryptoCultCurt

Appfolio MCP Server

get_property_performance_report

Retrieve financial performance metrics for properties by specifying date range and report format. Filter by property, owner, or group IDs.

Instructions

Retrieves the Property Performance report, showing financial performance metrics for properties within a specified date range. 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
property_visibilityNoFilter properties by status. Defaults to "active"active
propertiesNoFilter results based on properties, groups, portfolios, or owners. All ID fields must be numeric strings, not names.
report_formatYesFormat for the property performance report. Required.
period_fromYesThe start date for the reporting period (YYYY-MM-DD). Required.
period_toYesThe end date for the reporting period (YYYY-MM-DD). Required.
columnsNoArray of specific columns to include in the report. Note: Available columns depend on the report_format selected. Avoid generic names like "total_income" - check the API documentation for valid column names for this report.
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses the ID format constraint and that it retrieves a report. However, it lacks details on side effects, authentication requirements, rate limits, or response format, which are important for an agent invoking the tool.

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 extremely concise: two sentences plus a bolded critical note. It front-loads the purpose and immediately follows with essential usage constraint. Every sentence earns its place with no redundancy.

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?

Given 6 parameters, 3 required, nested objects, and no output schema, the description provides key context (ID format, column dependency) but does not describe the return structure or specific metrics included. For this complexity level, it is partially complete but could detail what financial metrics are in the report.

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?

Schema description coverage is 100%, but the description adds value by emphasizing that all ID parameters must be numeric strings and suggesting to use directory reports for lookup. It also warns that column names depend on report_format and to check API docs. This goes beyond the schema's built-in descriptions.

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 retrieves a 'Property Performance report' with financial metrics for a date range. The verb 'Retrieves' is specific, and the resource 'Property Performance report' distinguishes it from sibling 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 provides important usage guidance: IDs must be numeric strings, and recommends using directory reports to look up IDs if needed. It does not explicitly state when to use this report versus other financial reports, but the ID guidance is clear and 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