Skip to main content
Glama
CryptoCultCurt

Appfolio MCP Server

get_in_progress_workflows_report

Retrieve a report of in-progress workflows filtered by properties, units, tenants, owners, or other entities. Use numeric IDs from directory reports to specify filters.

Instructions

Returns a report of in-progress workflows based on the provided filters. IMPORTANT: All ID parameters (owners_ids, properties_ids, units_ids, etc.) must be numeric strings (e.g. '123'), NOT names. Use directory reports first to lookup IDs by name if needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
attachablesNoFilter results based on specific attached entities. All ID fields must be numeric strings, not names.
property_visibilityNoFilter properties by status. Defaults to "active"active
propertiesNoFilter results based on properties, groups, or portfolios. All ID fields must be numeric strings, not names.
process_templateNoFilter by specific process template name. Defaults to "All"All
workflow_stepNoFilter by specific workflow step name. Defaults to "All"All
assigned_userNoFilter by assigned user ID or "All". Defaults to "All". NOTE: Expects numeric user IDs (e.g. "4"), not user names. There is no user directory report available to lookup IDs by name.All
date_range_fromNoStart date for the due date range (YYYY-MM-DD)
date_range_toNoEnd date for the due date range (YYYY-MM-DD)
columnsNoArray of specific columns to include in the report
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the critical ID format constraint but does not mention side effects, response format, or other behavioral traits beyond filter application.

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 core purpose, the second provides a critical constraint and guidance. It is efficiently front-loaded with no unnecessary words.

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 no output schema and 9 parameters with nested objects, the description covers purpose and ID constraints but lacks an overview of the report content or usage context beyond filters. The detailed schema compensates partly.

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 baseline is 3. The description adds a global note about numeric string IDs, which is already reflected in individual parameter descriptions but aggregated for emphasis.

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 returns a report of in-progress workflows based on filters. It uses a specific verb ('Returns a report') and resource ('in-progress workflows'), distinguishing it from sibling tools like get_completed_workflows_report and get_cancelled_workflows_report.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides an important guideline about ID parameters being numeric strings and suggests using directory reports to look up IDs by name. However, it does not explicitly state when to use this tool versus other report tools or provide exclusions.

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