Skip to main content
Glama
ashev87

Propstack MCP

search_deals

Filter real estate deals by pipeline stage, contact, property, or broker. Track deal progress, find lost deals, and analyze cancellation reasons.

Instructions

Search and filter deals (contact↔property relationships) in Propstack.

Use this tool to:

  • Show all deals in a specific pipeline stage

  • Find deals for a contact or property

  • Track deal pipeline progress for a project

  • Find lost deals and cancellation reasons

  • Filter by broker, team, feeling (cold/warm/hot)

A "deal" represents an interested contact linked to a property at a specific stage in a sales/rental pipeline (e.g. Anfrage → Besichtigung → Reserviert → Notartermin → Verkauft).

Use include="client,property" to get expanded contact and property details in one request.

Common queries:

  • All active deals: category="qualified"

  • Lost deals this month: category="lost" + created_at_from

  • Deals for a property: property_id=123

  • Pipeline view: deal_pipeline_id + sort_by=deal_stage_id

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (default: 1)
orderNoSort order (default: desc)
includeNoComma-separated related data to expand: 'client', 'property', or 'client,property'
sort_byNoField to sort results by
team_idNoFilter by team ID
categoryNoDeal category: qualified (active), unqualified (not yet), lost (cancelled/rejected)
per_pageNoResults per page (default: 25)
broker_idNoFilter by assigned broker ID
client_idNoFilter by contact ID
feeling_toNoMaximum feeling score
project_idNoFilter by project ID
property_idNoFilter by property ID
feeling_fromNoMinimum feeling score (0=none, 1=cold, 2=warm, 3=hot)
created_at_toNoFilter deals created before this date (ISO 8601)
start_date_toNoFilter by deal start date to (ISO 8601)
deal_stage_idsNoFilter by deal stage IDs (pipeline steps)
created_at_fromNoFilter deals created after this date (ISO 8601)
start_date_fromNoFilter by deal start date from (ISO 8601)
client_source_idNoFilter by lead source ID
deal_pipeline_idNoFilter by deal pipeline ID
client_broker_idsNoFilter by contact's assigned broker IDs
property_broker_idsNoFilter by property's assigned broker IDs
show_archived_clientsNoInclude deals with archived contacts
reservation_reason_idsNoFilter by cancellation/reservation reason IDs
hide_archived_propertiesNoExclude deals with archived properties
Behavior4/5

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

No annotations provided, so description carries full burden. It explains the concept of deals, pipeline stages, categories, and the include parameter for expanded data. As a read operation, destructive behavior is not expected, but auth needs or rate limits are not mentioned. Still, it is transparent about core functionality.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is overly long with several paragraphs. While it provides comprehensive information, it could be tightened. The structure is logical (definition, usage, include option, examples) but lacks brevity.

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 25 parameters, no required ones, and no output schema, the description sufficiently covers the tool's purpose, filtering options, and use cases. It does not explain return format or pagination details beyond schema, but the provided context is adequate for agent selection.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description adds significant context beyond parameter descriptions: explains deal stages, feeling scores (cold/warm/hot), category meanings (qualified, unqualified, lost), and provides common query patterns. This enriches 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 searches and filters deals, defines a deal as a contact-property relationship in a pipeline, and lists specific use cases. It distinguishes from sibling tools like search_contacts or search_properties by focusing on deals.

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?

Explicitly lists when to use the tool with examples (e.g., show all deals in a pipeline stage, find deals for a contact/property, track pipeline progress). Lacks explicit when-not-to-use or direct comparisons to alternatives, but the examples provide strong guidance.

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/ashev87/propstack-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server