PropertyList: Spanish Property MLS

Qualify lead

qualify_lead

Stage qualifying a client, as the CRM's Qualified popup does: tags them as a buyer, seller or tenant, puts them on that pipeline board and takes them off the Lead board. Returns a preview, including what it will COST (a place on the Buyer board uses a free place or one credit), and an action_id; NOTHING changes or is charged until you call confirm_action with that id, after the agent has said yes.

Without board, the type comes from what the CRM already knows (the client's saved search, or a Vendor/Landlord tag); with neither, it asks for their details instead of guessing. With board, the client goes onto that board at its first step.

search saves what a buyer or tenant is looking for with the qualification, homes or commercial premises (offices, retail, a bar, a warehouse, a traspaso...), never both in one search.

Requires a linked PropertyList account: the change is made in the agent's own name, with their CRM permissions, so an agency API key alone cannot make it.

Input Schema

TableJSON Schema

Name	Required	Description
`board`	No	The board to put them on. Optional.
`search`	No	Optional: what a buyer or tenant is looking for, saved as their search when the qualification is confirmed.
`contact_id`	Yes	The client, from find_contacts or my_pipeline.

Output Schema

TableJSON Schema

Name	Required	Description
`status`	Yes
`details`	Yes
`summary`	Yes	What confirming will do, to show the agent.
`action_id`	Yes	Pass to confirm_action to make the change, or cancel_action to drop it.
`expires_at`	Yes	ISO 8601, UTC. After this the preview must be staged again.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 16, 2026

addedInput schema / properties / search

Added value: +{
+  "description": "Optional: what a buyer or tenant is looking for, saved as their search when the qualification is confirmed.",
+  "properties": {
+    "beds_min": {
+      "description": "Homes only.",
+      "type": "integer"
+    },
+    "build_min": {
+      "description": "Minimum built area in m².",
+      "type": "integer"
+    },
+    "location_ids": {
+      "description": "Area ids from autocomplete_location.",
+      "items": {
+        "type": "integer"
+      },
+      "type": "array"
+    },
+    "price_max": {
+      "type": "integer"
+    },
+    "price_min": {
+      "type": "integer"
+    },
+    "property_types": {
+      "description": "Homes (apartment, villa, penthouse, townhouse, country-house, plot) OR commercial premises (commercial, offices, retail, cafes-bars-restaurants, hotels-leisure, industrial-warehouses, garages-storage-rooms, buildings, commercial-land, businesses, or a type such as shop or warehouse).",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "tenure": {
+      "description": "A buyer of commercial premises who wants a traspaso (the lease and the business taken over).",
+      "enum": [
+        "traspaso"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedOct 6, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing the two-phase preview/confirm flow, that NOTHING changes or is charged until confirm_action is called, the cost model (free place or one credit on the Buyer board), and the auth requirement (linked PropertyList account, action taken in the agent's own name with CRM permissions, agency API key alone insufficient). This is exactly the behavioral context annotations cannot carry.

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?

Front-loads the core action and the preview/confirm constraint, and each paragraph earns its place (inference rules, search persistence, auth prerequisite). It runs long for three parameters, but the density is high and largely justified rather than padded.

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?

Covers the mutation's prerequisites (account linkage, permissions), the cost consequence, the confirm gate, and the conditional board/search semantics. An output schema exists, so return-value detail is correctly left out; nothing an agent needs to call this safely is missing.

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 the baseline is 3, but the description adds real meaning beyond the schema: the inference rules for `board` when omitted, that `board` places the client at the board's first step, and that `search` is persisted with the qualification but must not mix residential and commercial premises in one search.

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 (stage qualifying a client) and precisely what happens: tag as buyer/seller/tenant, place on a pipeline board, remove from the Lead board. It also distinguishes itself from siblings like confirm_action and move_pipeline_stage by describing the full board-transition effect.

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?

Explains conditional behavior clearly: without `board` the type is inferred from CRM knowledge (with a fallback of asking for details), and with `board` the client goes to that board's first step. It also names the mandatory follow-up (confirm_action with the returned action_id), giving a clear call sequence, though it never explicitly contrasts with siblings such as move_pipeline_stage.

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?