Skip to main content
Glama
ashev87

Propstack MCP

search_contacts

Search and filter CRM contacts by name, email, phone, and custom criteria. Manage leads, assess statuses, and retrieve full contact details with expandable fields.

Instructions

Search and filter contacts in Propstack CRM.

Use this tool to:

  • Find contacts by name, email, or phone number

  • List recent leads (sort by created_at desc)

  • Find uncontacted leads (last_contact_at is null)

  • Filter by broker assignment, status, tags, or GDPR status

  • Search across all contact fields with 'q' parameter

The 'q' parameter searches across: first name, last name, all emails, all addresses, and all phone numbers.

Phone search ('phone_number') ignores formatting — both 015712345678 and 0157-123-456-78 will match.

Returns paginated results. Use expand=true for full details including custom fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFulltext search across name, email, address, phone
pageNoPage number (default: 1)
emailNoSearch by email address
groupNoFilter by tag/group IDs (Merkmale)
orderNoSort order (default: desc)
ownerNoFilter for property owners
expandNoInclude full details and custom fields
statusNoFilter by contact status IDs
sort_byNoField to sort results by
sourcesNoFilter by lead source IDs (e.g. ImmoScout24, Website)
archivedNoArchive filter: '-1' = all (including archived), '1' = archived only. Omit for non-archived only (default).
languageNoFilter by language codes (e.g. 'de', 'en')
per_pageNoResults per page (default: 25)
broker_idNoFilter by assigned broker ID
newsletterNoFilter by newsletter opt-in
gdpr_statusNoGDPR status: 0=Keine Angabe, 1=Ignoriert, 2=Zugestimmt, 3=Widerrufen
project_idsNoFilter by associated project IDs
not_in_groupNoExclude contacts with these tag/group IDs
phone_numberNoSearch by phone number (formatting-insensitive)
created_at_toNoFilter contacts created before this date (ISO 8601)
updated_at_toNoFilter contacts updated before this date (ISO 8601)
accept_contactNoFilter by contact permission
home_countriesNoFilter by home country codes
created_at_fromNoFilter contacts created after this date (ISO 8601)
updated_at_fromNoFilter contacts updated after this date (ISO 8601)
include_childrenNoInclude sub-contacts in results
Behavior4/5

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

With no annotations, the description carries the full burden and effectively discloses key behaviors: pagination, phone search formatting insensitivity, cross-field search for 'q', and the expand parameter for full details. It does not cover rate limits or auth but adequately describes the search behavior.

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 and well-structured: a header line followed by bullet points listing use cases. Every sentence adds value, and it is front-loaded with the purpose. No fluff, appropriately sized for a search tool with many parameters.

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 the 26 parameters, lack of output schema, and no annotations, the description covers major use cases and adds behavioral details (phone search insensitivity, cross-field search). It mentions pagination and expand. It is nearly complete, though could mention default pagination values (but those are in schema). The sibling search_contacts_by_phone is a slight redundancy but not a gap.

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 parameters are documented. The description adds significant meaning beyond schema: explains the 'q' parameter searches across specific fields, details phone_number formatting insensitivity with examples, and clarifies the archived parameter's special values. This enriches 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 it is for searching and filtering contacts in the CRM, listing specific use cases (find by name/email/phone, list recent leads, etc.). It effectively distinguishes from sibling tools like get_contact (single contact) and search_contacts_by_phone (phone-specific).

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 scenarios for when to use the tool (e.g., find contacts, list recent leads). However, it does not explicitly state when not to use it or mention alternative tools like get_contact for a specific contact. The bullet points offer good context but lack exclusions.

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