Skip to main content
Glama
CryptoCultCurt

Appfolio MCP Server

get_guest_card_inquiries_report

Generate a filtered guest card inquiries report to analyze lead activity by properties, sources, statuses, and date range.

Instructions

Returns guest card inquiries report for the given filters. 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
property_visibilityNoFilter properties by visibility status. Defaults to "active"active
propertiesNoFilter results based on properties, groups, portfolios, or owners
guest_card_sourcesNoFilter by guest card sources. Defaults to ["all"]
guest_card_statusesNoFilter by guest card statuses. Defaults to ["all"]
guest_card_lead_typesNoFilter by guest card lead types. Defaults to ["all"]
assigned_userNoFilter by assigned user. Defaults to "All"All
assigned_user_visibilityNoFilter assigned users by visibility. Defaults to "active"active
guest_card_statusNoFilter by guest card status. Defaults to "open"open
filter_date_range_byNoWhich date field to use for filtering. Defaults to "inquiry"inquiry
received_on_fromYesStart date for the reporting period (YYYY-MM-DD). Required.
received_on_toYesEnd date for the reporting period (YYYY-MM-DD). Required.
columnsNoArray of specific columns to include in the report. Valid columns: name, email_address, phone_number, received, last_activity_date, last_activity_type, latest_interest_date, latest_interest_source, status, move_in_preference, max_rent, bed_bath_preference, pet_preference, monthly_income, credit_score, lead_type, source, property, unit, assigned_user, assigned_user_id, guest_card_id, guest_card_uuid, inquiry_id, occupancy_id, property_id, unit_id, notes, tenant_id, rental_application_id, rental_application_group_id, applicants, inquiry_type, total_interests_received, interests_received_in_range, showings, interest_to_showing_scheduled, showing_to_application_received, application_received_to_decision, application_submission_to_lease_signed, inquiry_to_lease_signed, inactive_reason, crm. 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. Only discloses the ID format requirement; does not mention side effects, authentication, rate limits, or output format. Lacks sufficient behavioral context.

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: first states purpose, second gives critical usage instruction. No fluff, front-loaded, every sentence earns its place.

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?

With 12 parameters, no output schema, the description is minimal. It does not explain the return format or pagination, but the parameters are well-documented in schema. Adequate but could be more complete.

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% with detailed parameter descriptions. The description adds a critical usage note about numeric IDs (already in schema but reinforced), but does not add significant new meaning beyond what schema provides.

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 'Returns guest card inquiries report for the given filters,' which specifies the verb, resource, and scope. It distinguishes from sibling report tools by focusing on guest card inquiries.

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 explicit guidance on using numeric IDs and referencing directory reports to look up IDs. However, no guidance on when to use this tool versus alternatives among many report 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