Skip to main content
Glama
CryptoCultCurt

Appfolio MCP Server

get_lease_expiration_detail_by_month_report

Retrieve lease expiration details by month with filters for properties, date range, unit status, and tags to manage upcoming renewals.

Instructions

Retrieves a report detailing lease expirations by month, filterable by properties, date range, and other criteria. IMPORTANT: All ID parameters (properties_ids, property_groups_ids, portfolios_ids, owners_ids) 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
from_dateYesThe start date for the reporting period (YYYY-MM-DD). Required.
to_dateYesThe end date for the reporting period (YYYY-MM-DD). Required.
propertiesNoFilter results based on properties, groups, portfolios, or owners
unit_visibilityNoFilter units by status. Defaults to "active"active
tagsNoFilter by unit tags (comma-separated string)
filter_lease_date_range_byNoWhich date field to use for the date range filter. Defaults to "Lease Expiration Date"Lease Expiration Date
exclude_occupancies_with_move_outNoExclude occupancies that have a move-out date. Defaults to "0" (false)0
exclude_month_to_monthNoExclude occupancies that are month-to-month. Defaults to "0" (false)0
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, unit, unit_tags, unit_type, move_in, lease_expires, lease_expires_month, market_rent, sqft, tenant_name, deposit, rent, phone_numbers, unit_id, occupancy_id, tenant_id, owner_agent, tenant_agent, rent_status, legal_rent, owners_phone_number, owners, last_rent_increase, next_rent_adjustment, next_rent_increase, lease_sign_date, last_lease_renewal, notice_given_date, move_out, tenant_tags, affordable_program, computed_market_rent. If not specified, all columns are returned.
Behavior3/5

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

No annotations are provided, so the description must carry the burden. It discloses filter capabilities and ID format requirements but omits output format, pagination, or rate limits. This is adequate but not comprehensive for a report 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?

Two sentences with no wasted words: first defines purpose, second provides critical usage guidance. Front-loaded and efficient.

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?

Given 9 parameters, nested objects, no output schema, and no annotations, the description covers primary purpose and key caveat. It could detail return format or add examples, but is sufficiently complete for typical use.

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 coverage is 100%, so baseline is 3. The description adds crucial context beyond the schema by emphasizing the numeric ID requirement and the need to use directory reports for ID lookup, enhancing parameter understanding.

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 specific report on lease expirations by month, distinguishing it from sibling reports like occupancy or rent roll. The verb 'retrieves' and resource 'report' with specific focus make purpose unambiguous.

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 advises that ID parameters must be numeric strings from directory reports, providing a clear prerequisite and lookup suggestion. It implies usage context but does not explicitly contrast with siblings.

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