Skip to main content
Glama
ashev87

Propstack MCP

update_contact

Update existing contact information, including personal details, broker assignment, tags, and GDPR status in Propstack CRM.

Instructions

Update an existing contact in Propstack CRM.

Use this tool to:

  • Update contact details after a call

  • Change broker assignment

  • Add or remove tags (Merkmale)

  • Update GDPR status

  • Change contact rating or status

Tag management options:

  • group_ids: replaces ALL tags with this list

  • add_group_ids: adds tags without removing existing ones

  • sub_group_ids: removes specific tags

Only provide the fields you want to change.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesContact ID to update
emailNoEmail address
phoneNoPhone number
ratingNoContact rating: 0 (none) to 3 (top priority)
companyNoCompany name
archivedNoArchive or unarchive the contact
languageNoLanguage code (e.g. 'de', 'en')
positionNoJob position/title
broker_idNoID of the assigned broker/agent
group_idsNoReplace ALL tags with this list of tag IDs
home_cityNoHome address: city
last_nameNoLast name
first_nameNoFirst name
newsletterNoNewsletter opt-in
salutationNoSalutation: mr (Herr) or ms (Frau)
descriptionNoFree-text description or notes
gdpr_statusNoGDPR status: 0=Keine Angabe, 1=Ignoriert, 2=Zugestimmt, 3=Widerrufen
home_streetNoHome address: street
office_cityNoOffice address: city
home_countryNoHome address: country code
add_group_idsNoAdd these tag IDs without removing existing tags
home_zip_codeNoHome address: postal code
office_streetNoOffice address: street
sub_group_idsNoRemove these tag IDs from the contact
academic_titleNoAcademic title (e.g. 'Dr.', 'Prof.')
accept_contactNoContact permission granted
office_countryNoOffice address: country code
office_zip_codeNoOffice address: postal code
client_source_idNoLead source ID
client_status_idNoContact status ID
home_house_numberNoHome address: house number
office_house_numberNoOffice address: house number
partial_custom_fieldsNoCustom field values as key-value pairs
Behavior3/5

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

No annotations are provided, so the description must cover behavioral traits. It mentions 'Only provide the fields you want to change,' implying a partial update, but lacks details on idempotency, error handling, or required permissions. For a mutation tool, this is minimal transparency.

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 well-structured with bullet points and sections. It is concise yet informative, front-loaded with purpose and use cases, and avoids unnecessary verbosity.

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 33 parameters and no output schema or annotations, the description fairly covers the update behavior and tag management. It lacks error/response info and validation details, but for a tool with many optional fields, it is mostly complete.

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

Parameters4/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 value by explaining tag management (group_ids, add_group_ids, sub_group_ids) and rating scale (0-3). For other parameters, the schema descriptions are clear, but the description does not elaborate on them further.

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 contact' and lists specific use cases (e.g., after a call, change broker, tags, GDPR). The verb-resource combination is explicit, and the tool is distinct from siblings like create_contact and delete_contact.

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 usage scenarios and guidance on tag management options. It tells when to use the tool after a call or for specific updates, but does not explicitly exclude cases or mention alternatives like create or delete for similar operations.

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