Get listing price and status updates in ChatGPT

Ask ChatGPT to notify you when a specific authorized MLS listing changes asking price or standard status. The available event is narrow: it does not watch every property field or discover new listings matching a search.

Before you start

Connect and authorize the B Square AgentOS MCP server in a ChatGPT host that supports the subscription tool. The configured server URL is:

https://api.bsquarerealty.com/mcp

The ChatGPT skills ZIP provides instructions; installing that ZIP alone does not connect your AgentOS account. Select the authorized MCP connection and the relevant skill plugin in your chat. The actual tools available in your host take precedence over screenshots or setup instructions from another version.

You need access to the listing you want to follow. Use an actual MLS reference or select a listing from a fresh authorized result. Do not invent a listing ID or assume a street address identifies exactly one listing.

1. Resolve the listing

Find MLS listing [MLS NUMBER] in B Square AgentOS and read its current details. Show me the address, listing ID, asking price, standard status, and source update time if available. If more than one listing matches, let me choose. Do not create a subscription yet.

Read the details before subscribing, especially when a property has been relisted. The subscription follows the selected listing ID, not every future listing at that address.

2. Request a notification-only subscription

After confirming the listing:

Subscribe to future asking-price and standard-status changes for AgentOS listing [VERIFIED LISTING ID].

When listing.updated arrives, notify me in this ChatGPT conversation with the listing identity, which supported fields changed, the previous and current values, and the event time if supplied. Re-read the listing when necessary to distinguish the event values from the latest available facts. State any missing values or gaps in history.

Do not contact clients, send email, generate marketing media, or publish anything. Confirm whether the saved subscription was actually created. If the subscription tool is unavailable or setup fails, tell me rather than claiming monitoring is active.

The current host tool is subscribe_to_events. Its trigger identifies one listing. This example documents the tool arguments, not a REST endpoint to paste into Zapier:

{
  "title": "Watch listing changes",
  "prompt": "When this listing's asking price or standard status changes, notify me in this ChatGPT conversation with the previous and current values. Report missing history. Do not contact anyone or generate or publish media.",
  "triggers": [
    {
      "event": "listing.updated",
      "params": {
        "listingId": "VERIFIED_LISTING_ID"
      }
    }
  ]
}

Use the real ID before execution. Creating the saved subscription is a real ongoing task, not a read-only preview.

3. Understand what will trigger it

The verified event payload tracks:

• listPrice: the asking price.
• standardStatus: the listing's standardized status.
• previous and current values for those fields.
• A listing ID, change sequence, and changed-field list.

A new photo, edited remarks, an open-house date, or another listing field does not trigger this subscription. A property newly matching “two bedrooms under $800,000” is also outside this single-listing event.

Updates depend on the MLS change reaching AgentOS and successful delivery to the host. Do not interpret “no notification” as proof that the property is unchanged, or promise instant delivery from the MLS source.

4. Confirm the right level of success

Check that the host returned a saved task or subscription confirmation for the correct listing. That proves registration was accepted, not that a future change has already been delivered.

The underlying MCP event service returns a renewal deadline (refreshBefore) and uses renewable subscriptions. Ongoing operation depends on the host maintaining that subscription and on continued account and listing access. The current source caps each server subscription lease at 24 hours; the chat prompt itself does not create a permanent background connection.

Do not change a real listing merely to test a notification. Confirm end-to-end delivery when an authorized real change occurs, or use an approved test environment. If a host cannot maintain subscriptions, ask it for a supported alternative rather than claiming the chat alone is watching in the background.

Change or stop the task

Find the saved task that watches AgentOS listing [LISTING ID]. Pause or delete that specific task, and confirm its actual state. Do not change other listing alerts.

Use the host's available task controls. Do not assume this is an AgentOS workflow or that disabling a workflow automatically deletes the ChatGPT subscription.

When you want actions instead of notifications

To start an AgentOS workflow when a listing changes, build and review a workflow using the separate listing.updated internal-event trigger. Its current contract can filter the listing and supported price/status changes. Publishing, enabling, and any downstream media generation or sending require their own reviewed scope. A notification-only subscription does not authorize those actions.

Verification: The production MCP tool catalog exposed listing.updated subscriptions during this review, and the source defines the event and delivery service. A live production listing change and its resulting ChatGPT notification were not tested. Tool visibility and source implementation must not be described as proven end-to-end delivery.