Skip to main content
Glama

PropertyList: Spanish Property MLS

by es.propertylist
OverviewDiscussionsAdmin

My listings

my_listings
Read-onlyIdempotent

List YOUR agency's own property listings (newest first), optionally filtered by status or a specific reference. Use for "show my listings" / "is reference X still online?". Requires a linked PropertyList account (or an agency API key); only ever returns the calling agency's own properties.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
statusNoListing status. Defaults to 'online'. 'draft' covers listings not yet published (new + in review); 'all' returns every status.online
referenceNoA specific listing reference. Optional.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
listingsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "listings": {
+      "items": {
+        "properties": {
+          "bathrooms": {
+            "type": "integer"
+          },
+          "bedrooms": {
+            "type": "integer"
+          },
+          "build_sqm": {
+            "type": "integer"
+          },
+          "id": {
+            "type": "integer"
+          },
+          "location": {
+            "type": "object"
+          },
+          "monthly_price": {
+            "type": "integer"
+          },
+          "photo": {
+            "type": "string"
+          },
+          "price": {
+            "description": "Headline price for the listing's transaction type; read with price_period.",
+            "type": "integer"
+          },
+          "price_period": {
+            "enum": [
+              "total",
+              "per_month",
+              "per_week"
+            ],
+            "type": "string"
+          },
+          "reference": {
+            "type": "string"
+          },
+          "sale_price": {
+            "type": "integer"
+          },
+          "status": {
+            "description": "online, offline, sold, new, inreview...",
+            "type": "string"
+          },
+          "updated_at": {
+            "description": "ISO 8601, UTC.",
+            "type": "string"
+          },
+          "weekly_price_from": {
+            "type": "integer"
+          }
+        },
+        "required": [
+          "id",
+          "reference"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "listings"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • changedInput schema / properties / status / description
      Previous value: -"Listing status. Defaults to 'online'."New value: +"Listing status. Defaults to 'online'. 'draft' covers listings not yet published (new + in review); 'all' returns every status."
    • changedInput schema / properties / status / enum
      Previous value: -[
-  "online",
-  "offline",
-  "sold",
-  "all"
-]New value: +[
+  "online",
+  "offline",
+  "sold",
+  "draft",
+  "all"
+]
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, closed-world behavior. The description adds genuinely non-structured context: the auth requirement, the agency-only scoping, and newest-first ordering. It stops short of describing result shape or pagination behavior, which is acceptable given an output schema exists.

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?

Three tight sentences, front-loaded with the core action and scope before the usage examples and prerequisites. No filler, though the parenthetical usage examples add a little bulk.

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?

For a read-only list tool with an output schema, the description covers what an agent needs: scope, ordering, filters, and the account prerequisite. The unmentioned limit parameter and absence of result-shape notes are minor given the output schema.

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 status enum is already richly documented in the schema itself. The description only restates that filtering by status or reference is possible and does not explain the limit cap or default, so it adds little beyond the structured fields.

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 ('List YOUR agency's own property listings') with ordering ('newest first') and scope ('only ever returns the calling agency's own properties'). This clearly distinguishes it from sibling search_properties, which covers all properties.

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 usage triggers ('show my listings' / 'is reference X still online?') and a prerequisite (linked PropertyList account or agency API key). It implicitly separates itself from the broad search sibling by scoping to the caller's own properties, though it never names the alternative explicitly.

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 toolsInspect
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