Propstack MCP by usefulapi

List or search contacts

propstack_list_contacts

Read-only

List or search CRM contacts (Kontakte). Returns business fields only (name, company, email, phone numbers, status, source, tags, owner, dates), never birth data, identity or tax numbers, income or portal tokens. Search by free text (name, email, address, phone), exact email, exact phone number, or filter by status, source, tag, owner and dates. Archived contacts are excluded unless archived is set. GET /contacts.

Input Schema

TableJSON Schema

Name	Required	Description
`per`	No	Results per page, 1-100 (default 25).
`page`	No	Page number, from 1 (default 1). Pass the previous reply's next_page.
`email`	No	Exact email address of the contact.
`order`	No	Sort direction.
`query`	No	Free-text search over first name, last name, emails, address and phone numbers.
`sort_by`	No	Sort field.
`tag_ids`	No	Only contacts with these tag (Merkmal) ids (see propstack_get_reference_data contact_tags).
`archived`	No	'only' = only archived contacts, 'include' = archived and active. Default: active only.
`broker_id`	No	Only contacts looked after by this user id (see propstack_list_users).
`source_ids`	No	Only contacts from one of these source ids (see propstack_get_reference_data contact_sources).
`status_ids`	No	Only contacts with one of these contact-status ids.
`phone_number`	No	Exact phone number (spaces and dashes are ignored).
`created_after`	No	Only contacts created at or after this ISO 8601 date-time.
`updated_after`	No	Only contacts updated at or after this ISO 8601 date-time.
`created_before`	No	Only contacts created at or before this ISO 8601 date-time.
`updated_before`	No	Only contacts updated at or before this ISO 8601 date-time.
`include_children`	No	Also return sub-contacts (contact persons of a company).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 12, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations cover readOnly/openWorld/destructive, and the description adds valuable PII transparency by listing what fields are returned and explicitly excluding sensitive data (birth data, identity/tax numbers, income, portal tokens). It also notes archived exclusion default, which is real behavioral context beyond annotations.

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?

Well-structured with the core purpose first, then field disclosure, then search modes. Slightly dense but every sentence carries information. The preamble 'never birth data...' is longer than strictly needed but justified by compliance sensitivity.

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

Completeness5/5

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

Given 17 optional parameters, no output schema, and annotations covering safety, the description adequately explains search/filter behavior, PII scope, and archived defaults. It is complete enough for an agent to invoke correctly without opening the schema.

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 goes further by explaining search semantics (free text searches name, email, address, phone; exact matching variants) and the archived parameter behavior, adding meaning beyond the schema's terse parameter 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?

States a specific verb+resource ('List or search CRM contacts') and immediately distinguishes itself from siblings like propstack_get_contact (single fetch) and propstack_create_contact (mutation). The endpoint reference 'GET /contacts' anchors it further.

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 details the available search and filter modes (free text, exact email, exact phone, status/source/tag/owner/date filters) which implies when to use this tool for discovery. However, it does not explicitly route to alternatives like propstack_get_contact for single lookups.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Propstack MCP by usefulapi tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

List or search contacts

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources