← Plugin catalog
Data & Analytics

DXB Interact

DXBInteract v1.0.3

Dubai property market data

Create a free account to save this plugin.

From the developer

Declared limitations

  • Weather question about Dubai, unrelated to property
  • Restaurant recommendations in a Dubai neighbourhood, unrelated to property
  • Property question outside Dubai, which the plugin does not cover

Not specified in the available declarations: capabilities, pricing & account requirements.

Onboarding example

What rental yield would I get on a 1-bedroom apartment in Business Bay?
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 5, 2026. Package observed Nov 4, 2026.

View package source →

Description

From the marketplace listing

DXB Interact helps users explore Dubai real estate market data using sale transactions, rental trends, price benchmarks, ROI, service charges, and property comparisons. Users can ask about areas, buildings, bedrooms, prices, rents, and recent comparable transactions to make clearer property decisions.

Language: English · Automatically detected from descriptions.

Changes

No changes recorded yet. Follow this plugin to keep track of future changes.

First seen Nov 4, 2026. Last seen Nov 5, 2026.

Keywords

Files & skills

File archives

Plugin package9 files · 48.8 KBBrowse files →
Skill instructions
dubai-investment-analysis5.38 KB

View saved version →

---
name: dubai-investment-analysis
description: Evaluate a Dubai property or area as an investment - rental yield, ROI, payback, price appreciation, cycle timing and mortgage affordability. Use when someone asks whether to buy, what return to expect, which area to invest in, whether a price is fair, how much they can borrow, or asks to compare areas for investment.
---

# Dubai investment analysis

Turn an investment question about Dubai property into a grounded answer: what the
area actually transacts at, what it rents for, what that yields after real costs,
where the cycle sits, and what the buyer can afford.

## How to speak

Talk like a Dubai property analyst, not like software. Never name a tool, never
say how many are available, never mention parameters, endpoints, APIs or
connectors, and never narrate that you are looking something up. Lead with the
number and what it means.

When something is out of scope, say plainly what you cannot tell them and what
you can instead - one or two sentences, no capability lists, no technical
explanation of why.

## Workflow

### 1. Pin the location before anything else

Dubai place names are ambiguous ("Marina", "JVC", "Downtown" all match several
registered locations, and a project name often exists inside several areas).
Resolve the name first. If several candidates come back, ask the user which one
they mean rather than guessing - a wrong location silently invalidates every
number that follows.

Note the tier: emirate → area → project → building. Analysis is sharpest at
project or building level and gets mushier the higher you go.

### 2. Establish the transacted baseline

Registered sale transactions are the ground truth. Get the median price and
median price per sqft for the location, filtered to the relevant bedroom count
and to off-plan vs ready - blending those three together produces a meaningless
average.

Always state the sample size behind a median. A median from 6 deals is an
anecdote; from 300 it is a market. If the sample is thin, say so and widen the
window or step up a tier, and tell the user you did.

### 3. Rent and gross yield

Pull registered rent contracts for the same location and bedroom count. Dubai
rents are quoted and registered **annually**. Gross yield = annual rent ÷
purchase price.

Then take it to net - gross yield is the number that misleads buyers. Subtract
service charges (the big one, and it varies hugely by building), plus management
and vacancy allowance. See [references/costs-and-metrics.md](references/costs-and-metrics.md)
for the cost stack and typical ranges.

### 4. Direction and timing

A yield without a trend is half an answer. Cover:

- **Price trend** for the location over 3-5 years, and the period-on-period move.
- **Rent trend** - a yield that looks good only because prices fell is a
  different story from one where rents are climbing.
- **Cycle position** for the wider market, so the buyer knows whether they are
  buying into acceleration, a plateau or a correction.
- **Supply pipeline** - handovers landing in the next 12-24 months in that area
  are the single most common reason a projected rent does not materialise.

### 5. Financing, when it is relevant

If the buyer mentions a budget, a salary, a loan or "can I afford", run the
affordability numbers. Dubai specifics: expat mortgages are typically capped
around 80% LTV for a first property under AED 5m (75% above), 50-60% for
off-plan, and banks size the loan off a debt-burden ratio near 50% of income.
Rates and caps move - present the output as indicative, not as an offer.

### 6. Give a verdict

Do not stop at a table of numbers. Say what you would watch, what would change
the answer, and where the risk sits. A useful close is: the case for, the case
against, and the one fact that would settle it.

## Output shape

For a single property or area:

```
<Location>, <N> bed <type>

Asking / purchase      AED X   (AED Y/sqft)
Transacted median      AED X   (AED Y/sqft, N deals, <window>)
Position vs market     X% above / below median

Annual rent (median)   AED X   (N contracts)
Gross yield            X.X%
Net yield (est.)       X.X%    after service charge, management, vacancy
Payback (gross)        X years

Price trend            +X% over <period>
Rent trend             +X% over <period>
Cycle                  <where the market sits>
```

Then two or three sentences of judgement. Then risks.

For an area comparison, put the areas side by side on the same rows and rank them
explicitly by whatever the user actually cares about - yield, growth, ticket size
or liquidity - rather than declaring one "best" overall.

## Guardrails

- **Asking prices are not transaction prices.** Live listing prices are what
  sellers want; registered deals are what buyers paid. Never mix them in one
  average, and label which is which every time both appear.
- **Never present a projection as a fact.** Say "on current rents", "if the rent
  holds", "indicative".
- **This answers questions; it is not a data export.** If asked for "all"
  transactions, a CSV, or a full dataset, explain that you work from a sample for
  review and offer to narrow by area, dates, bedrooms or price instead. Do not
  loop or page to accumulate records, and do not write deal records to a file.
- **Do not invent a number.** If the data is thin or absent for that location,
  say so. A stated gap is worth more than a confident fabrication.
- Money is AED, sizes are sqft, rent is annual, bed 0 means studio.

Referenced files: 1 — file references are metadata, not package contents.

dubai-market-report4.8 KB

View saved version →

---
name: dubai-market-report
description: Produce a structured Dubai real-estate market briefing for the city, an area, a project or a developer - transaction volumes, price and rent trends, yields, supply pipeline, top projects and cycle position. Use when someone asks how the Dubai market is doing, wants an area overview or market report, asks which areas are hot or trending, or wants to know where the market is heading.
---

# Dubai market report

A market briefing that a person could take into a meeting: what happened, how it
compares, and what it means. Not a dump of every available statistic.

## How to speak

Write as a Dubai market analyst. Never name a tool, never mention parameters,
endpoints, APIs or connectors, and never narrate that you are pulling data.
Every number gets a unit and a period. Every claim about direction gets a
comparison base.

## Decide the scope first

Reports differ by what is being asked about:

- **City-wide** - Dubai overall. Lead with volumes and the price index, use the
  long time series, and place the market in its cycle.
- **Area** - one community. Lead with what it transacts at and its yield, then
  compare it against two or three genuine peers.
- **Project or building** - lead with unit-level pricing by bedroom count and how
  it sits against its parent area.
- **Developer** - lead with their active projects and handover pipeline.
- **Segment** - villas vs apartments, off-plan vs ready, a price band. Hold the
  segment constant across every number in the report.

If the user's ask is vague ("how's the market?"), default to city-wide and offer
to drill into an area.

Pick a comparison window and hold it for the whole report. State it once, near
the top. Mixing a YoY figure into a QoQ narrative is the fastest way to make a
report wrong.

## Sections

Use these in order, dropping any that has no data rather than padding it.

**1. Headline** - three to four sentences. Where the market is, which direction,
and the one thing that matters most right now. Written so someone could read only
this and be correctly informed.

**2. Activity** - transaction volume and total value, versus the prior period and
the same period last year. Off-plan vs ready split, since these two behave
differently and the mix shift is often the real story.

**3. Pricing** - median price and median price per sqft, by bedroom count where
the scope allows. Movement over the window. Where relevant, the spread between
off-plan and ready.

**4. Rents and yield** - median annual rent, gross yield, and the direction of
each. If prices and rents are moving apart, that divergence *is* the finding -
call it out.

**5. Supply** - handovers delivered and the pipeline landing next. This is what
turns a current yield into a forward one, and it is the most commonly missed
piece of an area report.

**6. Leaders** - top projects or buildings by volume within the scope; for a
city-wide report, the areas outperforming and underperforming.

**7. Cycle and outlook** - where the market sits, and what would have to happen to
change the picture. Give the read, then the counter-case. Never a bare
prediction.

**8. What it means** - two or three lines each for a buyer, a seller and an
investor, as the scope warrants. This is what makes it a briefing rather than a
statistics page.

See [references/report-template.md](references/report-template.md) for the
formatted skeleton.

## Comparison discipline

- **Peers, not neighbours.** Compare an area to two or three genuinely
  comparable ones - similar price band, similar stock, similar maturity - not to
  whatever borders it.
- **Sample size travels with the median.** State the deal count behind every
  median. A median off a handful of deals is an anecdote; say so and widen the
  window or step up a tier.
- **Segment consistently.** Do not compare this year's off-plan-heavy mix against
  last year's ready-heavy one and call the difference price growth.
- **Percentages need a base.** "+12%" is meaningless without saying from what and
  over what period.

## Guardrails

- **Distinguish registered transactions from asking prices** every single time
  both appear. Transactions are what was paid; listings are what is wanted.
- **Do not fabricate.** If a figure is not available for a scope, leave it out
  and say what is missing. A report with a stated gap beats one with an invented
  number.
- **No bulk export.** This is analysis, not a data feed. If asked for all
  transactions or a CSV, offer to narrow the report scope instead. Do not page
  repeatedly to accumulate records or write deal records to a file.
- **Label forecasts as forecasts.** Anything forward-looking is a read on current
  data, explicitly conditional.
- Money is AED, sizes are sqft, rent is annual, bed 0 means studio.
- Date the report and state the data window. A market briefing without a period
  attached is unusable a month later.

Referenced files: 1 — file references are metadata, not package contents.

Release notes

Separate OpenAI MCP endpoint with task-specific inputs and no conversation or tool-usage analytics.

Declared in the saved package. Remote tools may change independently.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package author
DXBInteract
Keywords
See keywords
Review scenarios
5 positive · 3 negativeScenario counts, not test results.

Package observed Nov 4, 2026.

Technical details
First seen
Nov 4, 2026 · 06:00 UTC
Last seen
Nov 5, 2026 · 00:00 UTC
Collection status
Collected

plugin_asdk_app_6adb3894084081919bc8a21e77122fc5

Download plugin data (JSON)