Skip to main content
Glama
ashev87

Propstack MCP

create_property

Add a property to Propstack CRM from acquisition calls or owner inquiries, linking contacts and specifying status, type, price, and location.

Instructions

Create a new property (Objekt) in Propstack CRM.

Use this tool to:

  • List a new property from an acquisition call

  • Create a listing from an owner inquiry

  • Add a property to a project

Use get_property_statuses to look up valid status IDs. Use the relationships_attributes array to link an owner contact on creation.

rs_type values: APARTMENT, HOUSE, TRADE_SITE, GARAGE, SHORT_TERM_ACCOMODATION, OFFICE, GASTRONOMY, INDUSTRY, STORE, SPECIAL_PURPOSE, INVESTMENT.

rs_category provides sub-types (e.g. PENTHOUSE, VILLA, MAISONETTE for APARTMENT/HOUSE).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNoLatitude
lngNoLongitude
cityNoCity
floorNoFloor number
priceNoPurchase price (EUR)
titleNoProperty title / headline
statusNoProperty status ID (use get_property_statuses to look up)
streetNoStreet name
countryNoCountry code (e.g. 'DE')
rs_typeNoProperty type (e.g. APARTMENT, HOUSE, OFFICE)
courtageNoCommission amount or percentage
zip_codeNoPostal code
base_rentNoBase rent (EUR/month)
broker_idNoAssigned broker ID
plot_areaNoPlot area (m²)
other_noteNoAdditional notes text
project_idNoProject ID this property belongs to
total_rentNoTotal rent including utilities (EUR/month)
object_typeNoObject category: LIVING, COMMERCIAL, or INVESTMENT
rs_categoryNoProperty sub-type (e.g. PENTHOUSE, VILLA, MAISONETTE, SINGLE_FAMILY_HOUSE)
house_numberNoHouse number
living_spaceNoLiving space (m²)
courtage_noteNoCommission details/notes
location_noteNoLocation description text
marketing_typeNoMarketing type: BUY (Kauf) or RENT (Miete)
furnishing_noteNoFurnishing/equipment description text
number_of_roomsNoNumber of rooms
description_noteNoProperty description text (HTML allowed)
construction_yearNoYear of construction
number_of_bed_roomsNoNumber of bedrooms
number_of_bath_roomsNoNumber of bathrooms
partial_custom_fieldsNoCustom field values as key-value pairs
relationships_attributesNoLink contacts on creation, e.g. [{internal_name: "owner", related_client_id: 123}]
Behavior3/5

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

With no annotations, the description discloses some behavior (creation with optional owner linking and status lookup) but omits details on side effects, idempotency, auth requirements, or response format. It adds moderate value beyond the tool name.

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

Conciseness4/5

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

The description is well-structured with bullet points and front-loaded purpose. It efficiently covers key aspects, though some sentences could be merged for brevity.

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?

For a creation tool with 33 parameters and no output schema, the description does not explain the return value (e.g., created property ID) or error handling. It covers parameter usage well but lacks output and completeness details.

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 each parameter has a description. The description adds contextual guidance (e.g., listing rs_type enum values and examples for rs_category) but mostly reinforces schema info. Baseline of 3 is appropriate.

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 'Create a new property (Objekt) in Propstack CRM' and provides specific use cases like 'List a new property from an acquisition call', distinguishing it from sibling tools such as update_property or search_properties.

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 offers clear usage context (acquisition, owner inquiry, project addition) and directs to use get_property_statuses for status IDs and relationships_attributes for linking owners. It does not explicitly state when not to use this tool, but the context is sufficient.

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