Skip to main content
Glama
ashev87

Propstack MCP

update_search_profile

Update an existing Propstack search profile to adjust budget, cities, room count, features, or activate/deactivate it.

Instructions

Update an existing search profile in Propstack.

Use this tool to:

  • Expand or narrow budget ("increase max price to 450k")

  • Add or change cities ("also look in Potsdam")

  • Adjust room count or space requirements

  • Toggle feature requirements (add/remove balcony, lift, etc.)

  • Activate or deactivate the profile

Only provide the fields you want to change.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSearch profile ID to update
latNoLatitude for radius search center
lngNoLongitude for radius search center
liftNoLift/elevator required: 'true', 'false', or omit for any
noteNoFree-text note about this search profile
floorNoMinimum floor
priceNoMinimum purchase price (EUR)
activeNoWhether the search profile is active (default: true)
cellarNoCellar required: 'true', 'false', or omit for any
citiesNoCity names to search in (e.g. ['Berlin', 'Potsdam'])
gardenNoGarden required: 'true', 'false', or omit for any
radiusNoSearch radius in meters from lat/lng center
rentedNoCurrently rented: 'true', 'false', or omit for any
balconyNoBalcony required: 'true', 'false', or omit for any
regionsNoRegion names to search in
floor_toNoMaximum floor
price_toNoMaximum purchase price (EUR)
rs_typesNoProperty types (e.g. ['APARTMENT', 'HOUSE'])
base_rentNoMinimum base rent (EUR/month)
client_idNoContact ID (rarely changed)
group_idsNoTag/group IDs to assign
plot_areaNoMinimum plot area (m²)
total_rentNoMinimum total rent (EUR/month)
base_rent_toNoMaximum base rent (EUR/month)
living_spaceNoMinimum living space (m²)
location_idsNoPropstack location/district IDs
plot_area_toNoMaximum plot area (m²)
yield_actualNoMinimum actual yield (%)
price_per_sqmNoMinimum price per m² (EUR)
rs_categoriesNoProperty categories (e.g. ['APARTMENT_NORMAL', 'HOUSE_DETACHED'])
total_rent_toNoMaximum total rent (EUR/month)
marketing_typeNoMarketing type: BUY (Kauf) or RENT (Miete)
living_space_toNoMaximum living space (m²)
number_of_roomsNoMinimum number of rooms
yield_actual_toNoMaximum actual yield (%)
built_in_kitchenNoBuilt-in kitchen required: 'true', 'false', or omit for any
price_multiplierNoMinimum price multiplier (Vervielfältiger)
price_per_sqm_toNoMaximum price per m² (EUR)
construction_yearNoMinimum construction year
number_of_rooms_toNoMaximum number of rooms
number_of_bed_roomsNoMinimum number of bedrooms
price_multiplier_toNoMaximum price multiplier
construction_year_toNoMaximum construction year
number_of_bed_rooms_toNoMaximum number of bedrooms
Behavior3/5

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

With no annotations, the description carries the burden. It indicates mutation ('update', 'activate/deactivate') but does not disclose auth requirements, rate limits, side effects, or whether updates are partial (PATCH-like).

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 concise, front-loaded with the tool's purpose, and uses a bullet-like list for examples. Every sentence adds value without unnecessary detail.

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?

The description covers parameters well but lacks information about the return value (no output schema) and does not mention authentication or rate limits. For a complex tool with 44 parameters, this is a moderate gap.

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 descriptions for all 44 parameters, so the description adds minimal extra meaning beyond listing categories of changes. Baseline 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 the tool updates an existing search profile and lists specific use cases (expand budget, change cities, etc.), distinguishing it from sibling tools like create_search_profile and delete_search_profile.

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 gives explicit guidance on when to use the tool and advises to provide only changing fields, but does not explicitly contrast with other tools or state when not to use it.

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