Skip to main content
Glama
CryptoCultCurt

Appfolio MCP Server

get_work_order_report

Generate work order reports filtered by property, status, priority, date range, and other criteria for tracking maintenance and costs.

Instructions

Generates a report on work orders. IMPORTANT: All ID parameters (unit_ids, property_id, 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
unit_idsNoOptional. Filter by specific unit IDs.
propertyNoOptional. Filter by a single property ID.
parties_idsNoOptional. Filter by specific occupancy IDs.
party_contact_infoNoOptional. Filter by a specific vendor ID (company).
assigned_userNoFilter by assigned user ID or "All". Defaults to "All".All
created_byNoFilter by creator user ID or "All". Defaults to "All".All
priorityNoFilter by priority. Defaults to "All".All
from_inspectionNoOptional. Filter by whether the work order originated from an inspection. Defaults to false.
current_estimate_approval_statusNoFilter by estimate approval status. Defaults to "All".All
work_order_statusesNoOptional. Filter by specific work order status IDs.
work_order_typesNoOptional. Filter by specific work order types.
unit_turn_categoryNoFilter by unit turn category. Defaults to ["all"].
status_date_range_fromNoOptional. Start date for status date range filter (YYYY-MM-DD).
status_date_range_toNoOptional. End date for status date range filter (YYYY-MM-DD).
status_dateNoField to use for status date range filtering. Defaults to "all".all
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_address, unit_street, unit_street2, unit_city, unit_state, unit_zip, priority, work_order_type, service_request_number, service_request_description, home_warranty_expiration, work_order_number, job_description, instructions, status, vendor_id, vendor, unit_id, unit_name, occupancy_id, primary_tenant, primary_tenant_email, primary_tenant_phone_number, created_at, created_by, assigned_user, estimate_req_on, estimated_on, estimate_amount, estimate_approval_status, estimate_approved_on, estimate_approval_last_requested_on, scheduled_start, scheduled_end, work_completed_on, completed_on, last_billed_on, canceled_on, amount, invoice, unit_turn_id, corporate_charge_amount, corporate_charge_id, discount_amount, discount_bill_id, markup_amount, markup_bill_id, tenant_total_charge_amount, tenant_charge_ids, vendor_bill_amount, vendor_bill_id, vendor_charge_amount, vendor_charge_id, inspection_id, inspection_date, work_order_id, service_request_id, recurring, submitted_by_tenant, requesting_tenant, maintenance_limit, status_notes, follow_up_on, vendor_trade, unit_turn_category, work_order_issue, survey_id, vendor_portal_invoices
Behavior2/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 only states the tool generates a report but does not disclose behavioral aspects like output format, pagination, authentication requirements, or performance implications. For a report generating tool, this is insufficient.

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 sentences: the first states the purpose directly, and the second is a crucial usage note. No unnecessary words, perfectly front-loaded and scannable.

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 17 parameters, 4 enums, and no output schema, the description is minimal. It covers the main purpose and a key nuance, but lacks info on default report behavior, output structure, or any limits. Acceptable but could be expanded.

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?

The input schema covers 100% of parameters with descriptions, but the description adds critical meaning by specifying that all ID parameters must be numeric strings and not names. This goes beyond the schema, which only describes types. Without this note, the tool could be misused.

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 'Generates a report on work orders,' specifying the verb (generates) and resource (work orders). This distinguishes it from sibling tools like get_work_order_labor_summary_report, which focuses on labor summaries. The purpose is 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 provides explicit guidance on ID parameter format (must be numeric strings) and directs users to use directory reports for ID lookup. However, it does not explicitly state when to avoid this tool (e.g., for non-report workflows) or offer alternative 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