PropertyList: Spanish Property MLS

Find contacts

find_contacts

Read-onlyIdempotent

Search YOUR agency's CRM contacts by name, company, email or phone. Use to look a person up before logging a note or to check if they're already in the CRM. Requires a linked PropertyList account (or an agency API key); only ever searches the calling agency's own contacts.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes	Name, company, email or phone fragment to search for.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`contacts`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "contacts": {
+      "items": {
+        "properties": {
+          "company_name": {
+            "type": "string"
+          },
+          "created_at": {
+            "description": "ISO 8601, UTC.",
+            "type": "string"
+          },
+          "emails": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "id": {
+            "description": "contact_id, for log_note.",
+            "type": "integer"
+          },
+          "name": {
+            "type": "string"
+          },
+          "phones": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "pipelines": {
+            "description": "Board name to the stage this contact is in, in the agency's own stage names.",
+            "type": "object"
+          },
+          "surname": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "count": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "count",
+    "contacts"
+  ],
+  "type": "object"
+}

First observedJul 27, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the auth requirement (linked account or API key) and the strict tenancy scoping ('only ever searches the calling agency's own contacts'), which materially changes how an agent should interpret empty results.

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?

Three tight sentences that lead with what the tool does, then when to use it, then the auth/scoping constraint. No filler, no redundancy; each sentence carries distinct information.

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?

An output schema exists so return values need no explanation, and annotations cover the safety profile. The description covers purpose, usage trigger, auth prerequisites, and tenancy scoping — everything an agent needs to decide when to call it and how to read the result boundary.

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 description coverage is 50%: the query parameter is documented in-schema, but limit is only constrained structurally (default 20, max 50) with no prose. The description restates the query semantics (name/company/email/phone) but says nothing about limiting result count, so it neither compensates for the gap nor adds meaning beyond the schema.

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 precise verb+resource+scope: search the calling agency's own CRM contacts, with the searchable fields (name, company, email, phone) enumerated. This clearly distinguishes it from siblings like create_contact, my_leads, and find_properties_by_description without needing to open any schema.

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?

Gives concrete when-to-use context ('look a person up before logging a note or to check if they're already in the CRM') and names a prerequisite (linked PropertyList account or agency API key). It does not explicitly name create_contact as the write-side alternative, so the routing guidance is strong but not fully explicit.

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?