Skip to main content
Glama
ashev87

Propstack MCP

update_property

Update an existing property in Propstack CRM by modifying its price, status, description, broker, project, or custom fields. Provide only the fields you want to change.

Instructions

Update an existing property in Propstack CRM.

Use this tool to:

  • Update the price or rent

  • Change property status (e.g. mark as reserved or sold)

  • Edit description texts

  • Assign to a different broker or project

  • Update custom fields

Only provide the fields you want to change. Use get_property_statuses to look up valid status IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesProperty ID to update
latNoLatitude
lngNoLongitude
cityNoCity
floorNoFloor number
priceNoPurchase price (EUR)
titleNoProperty title / headline
statusNoProperty status ID (use get_property_statuses)
streetNoStreet name
countryNoCountry code
rs_typeNoProperty type
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
total_rentNoTotal rent (EUR/month)
object_typeNoObject category
rs_categoryNoProperty sub-type
house_numberNoHouse number
living_spaceNoLiving space (m²)
courtage_noteNoCommission details
location_noteNoLocation description text
marketing_typeNoMarketing type: BUY or RENT
furnishing_noteNoFurnishing description text
number_of_roomsNoNumber of rooms
description_noteNoProperty description text
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
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions updating an existing property and partial updates ('Only provide the fields you want to change'), but does not disclose side effects, authorization needs, rate limits, or what happens if the property does not exist.

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 concise, front-loaded with purpose, and efficiently covers key points in a few sentences. It could benefit from slightly more structured formatting.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 33 parameters, no output schema, and no annotations, the description lacks completeness. It does not cover error handling, response format, or required permissions for updates, leaving significant gaps for a complex mutation tool.

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 some context by grouping update categories (price, status, etc.) and mentioning custom fields, but does not significantly enhance understanding beyond the schema descriptions.

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 'Update an existing property in Propstack CRM' and lists specific use cases (update price, status, etc.). It differentiates from sibling tools like 'create_property' and 'get_property'.

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 clear context on when to use the tool by listing typical update actions and advising to use 'get_property_statuses' for valid status IDs. However, it does not explicitly state when not to use this tool versus alternatives.

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