Skip to main content
Glama

PropertyList: Spanish Property MLS

My leads

my_leads
Read-onlyIdempotent

List recent enquiries (leads) for YOUR agency's CRM - newest first. Use when the agent asks what has just come in (e.g. "what came in today?").

This is the enquiry inbox: an enquiry that arrived from the portal, a website or a microsite. Once an agent starts working a person they live on a pipeline board instead - for those, use my_pipeline. An agency that works everything off the boards can have a busy CRM and an empty inbox here, which is not the same as having no leads.

Requires a linked PropertyList account (or an agency API key); only ever returns the calling agency's own leads.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
sinceNoISO date/time - only leads created on or after this. Optional.
property_referenceNoOnly leads about this listing reference. Optional.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
leadsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "count": {
      +      "type": "integer"
      +    },
      +    "leads": {
      +      "items": {
      +        "properties": {
      +          "contact_id": {
      +            "type": "integer"
      +          },
      +          "created_at": {
      +            "description": "ISO 8601, UTC.",
      +            "type": "string"
      +          },
      +          "email": {
      +            "type": "string"
      +          },
      +          "id": {
      +            "type": "integer"
      +          },
      +          "lead_type": {
      +            "type": "string"
      +          },
      +          "message": {
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "phone": {
      +            "type": "string"
      +          },
      +          "property_reference": {
      +            "type": "string"
      +          },
      +          "status": {
      +            "description": "new, active, closed_converted or closed_not_converted.",
      +            "type": [
      +              "string",
      +              "integer"
      +            ]
      +          }
      +        },
      +        "required": [
      +          "id"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "count",
      +    "leads"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description adds context beyond them: an authentication prerequisite (linked PropertyList account or agency API key), tenancy scoping (only ever returns the calling agency's own leads), and result ordering. That is exactly the kind of behavioral detail structured fields 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-loaded with the action and ordering, then the trigger, then the sibling contrast and the caveat. Slightly longer than strictly necessary (the CRM/inbox framing is repeated), but every sentence carries information and none is filler.

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. Combined with the auth requirement, tenancy scope, ordering, and the inbox-vs-pipeline mental model, an agent has everything needed to call this correctly and to interpret an empty result.

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?

The description says nothing about limit, since, or property_reference. Schema coverage is a middling 67% – since and property_reference are documented in the schema while limit relies on default/min/max alone – so the schema does most of the work and the description neither compensates for nor extends it. Baseline 3 is appropriate.

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 recent enquiries (leads) for YOUR agency's CRM') plus ordering ('newest first'), and explicitly distinguishes itself from the sibling my_pipeline. An agent can tell it apart from my_pipeline or my_listings without opening either schema.

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?

Gives an explicit trigger ('Use when the agent asks what has just come in'), names the alternative tool for the other case (my_pipeline), and adds a genuine exclusion-style caveat: an agency working off boards can have a busy CRM and an empty inbox, which is not the same as no leads. Nothing is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources