PropertyList: Spanish Property MLS

Match buyer to inventory

match_buyer_to_inventory

Read-onlyIdempotent

The listings that fit one client's search in YOUR agency's CRM: your own listings first, then shared MLS listings your agency can sell, newest first. Each listing says whether it is your own.

Uses the client's saved search (or, if none is saved, the search their latest debrief described), the same search the CRM runs for that client. A client with no search returns an explanation rather than a guess; set one up in the CRM or ask the agent for the brief and use search_properties instead.

Get the contact_id from find_contacts. Call get_contact first if you need to know what has already been sent to them.

Requires a linked PropertyList account (or an agency API key); only the calling agency's clients that the caller may see in the CRM.

Input Schema

Name	Required	Description	Default
`limit`	No
`language`	No	Language for listing titles and excerpts.	en
`contact_id`	Yes	The client, from find_contacts or my_pipeline.

Output Schema

Name	Required	Description	Default
`error`	No
`total`	Yes
`limits`	No
`search`	No
`contact_id`	Yes
`properties`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026
- addedOutput schema / properties / properties / items / properties / buildable_sqm
```
Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}
```

Changed2 schema fields changedOct 13, 2026

addedOutput schema / properties / error

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / limits

Added value: +{
+  "type": [
+    "object",
+    "null"
+  ]
+}

AddedOct 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Goes well beyond the readOnly/idempotent annotations: it discloses the result ordering (own listings first, then shared MLS, newest first), a per-listing ownership flag, the no-search behavior (explanation, not a guess), and the auth prerequisite (linked PropertyList account or agency API key). Only missing detail is what happens with the limit cap and whether partial results are common.

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 front-loaded with scope and ordering in the first sentence, then prerequisites and fallbacks in descending priority. Slightly verbose in places ('the same search the CRM runs for that client' repeats the prior clause), but every paragraph carries distinct information.

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?

With an output schema present, the description correctly omits return-value structure while still covering ordering, ownership flagging, and auth requirements. The only real gap is the limit parameter's effect on result completeness.

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 67% and the description only adds sourcing guidance for contact_id ('from find_contacts'). The limit parameter (default 5, max 20) is not explained in either the schema or the description, so truncation behavior is left implicit.

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 and resource ('listings that fit one client's search') and pins the scope to the caller's agency CRM with an explicit ordering rule. It is clearly distinguishable from match_inventory_to_buyers (reverse direction) and search_properties (used when no saved search exists).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the saved-search input, the fallback to the latest debrief, and the exact failure mode when neither exists, with the named alternative (search_properties) to use instead. Also routes the agent to find_contacts for contact_id and get_contact to check sending history.

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

All PropertyList: Spanish Property MLS 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.

Resources

Need Help?