Skip to main content
Glama

Market Data

by com.timzinin.api

New Listing Alert

re-new-listing-alert

Watches a property portal for a saved filter and returns only the listings that appeared since the previous check. The first run on a new filter creates the baseline and says so. — $0.05/call, x402 (USDC on base).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterYesThe search filter to pass to the chosen portal's own Actor input — same field names as that Actor's own input schema (e.g. Krisha.kz wants {"queries":["sale:apartment:almaty"]}, Rightmove wants {"location_identifier":"REGION^87490","deal_type":"sale"}). See the README's Input table for every portal's fields. Any "max_items"/"max_pages" you set here are capped at 10/2 regardless of the portal's own limits, to keep each check fast and cheap.
portalYesWhich of our own live real-estate Actors this watch calls. Each portal's own filter fields differ — see the Input section of the README for the exact fields each one expects.krisha-kz
max_itemsNoCaps how many NEW-listing rows a single run will deliver and charge for, even if more were found.
baseline_keyNoA name for THIS watch, so you can run several independent watches (different portals and/or filters) from one Actor without one overwriting another's memory of what's already been seen. Each name is scoped to YOUR OWN Apify account. The prefilled value is only there so this Actor's own daily test run has a stable, obviously-a-test name; replace it with your own watch name.

TDQS

A4/5.0
Behavior4/5

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

Annotations provide basic flags (readOnlyHint=false, openWorldHint=true, etc.), but the description adds valuable behavioral context: it maintains a baseline across runs, first run creates the baseline and says so, and there is a cost per call (USDC on base). These details go beyond the schema and annotations, making the tool's operational semantics clearer.

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?

The description is extremely concise: two sentences plus a cost note. It front-loads the core purpose (watch and return new listings) and adds the critical baseline behavior without unnecessary verbosity.

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?

Given the tool's complexity (stateful baseline, multiple portals, nested filter object) and no output schema, the description adequately covers the most important behavioral aspects: baseline creation, incremental results, and cost. It does not detail return format, but the schema covers input specifics, so the description is reasonably complete.

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 input schema has 100% description coverage for all four parameters, so the description doesn't need to compensate. The tool description adds no extra parameter-level meaning beyond what the schema already provides, and it doesn't explain the filter JSON structure or portal-specific 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?

The description clearly states a specific action: watches a property portal for a saved filter and returns only new listings since the previous check. This distinguishes it from sibling alert tools by explicitly focusing on property portals and incremental listing retrieval.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage (for getting new listings on property portals since last check) and explains first-run baseline behavior, but it does not explicitly state when to use this tool over alternatives or mention any exclusions. Sibling tools like job-alert or tender-alert are not referenced.

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

All Market Data toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation3/5

Many tools are distinct by region/source (e.g., otodom-warsaw vs. imovirtual-lisbon), but there are overlapping categories: multiple real estate, job, SEC, and crypto tools. Watchers/alerts (job-alert, re-new-listing-alert, tender-alert) could be confused with their corresponding search tools, and token tools (live-price-oracle, token-launch-radar, rug-pull-scorer) have similar purposes.

Naming Consistency2/5

Names follow no consistent pattern: some are hyphenated source-location (emlakjet-istanbul), some are generic descriptors (job-alert, pricing_info uses underscore), and some are verbose phrases (official-gazette-regulatory-action-router). There is no consistent verb_noun or noun structure, making it hard to predict what a tool does from its name.

Tool Count2/5

With 36 tools, the server is in the 'too many' range (25+). The broad 'Market Data' theme partially justifies the count, but it feels bloated with many single-country listings and overlapping watchers that could be consolidated.

Completeness3/5

The domain is loosely defined as 'market data,' spanning real estate, jobs, tenders, SEC filings, crypto, and clinical trials. While it covers niche areas well, there are notable gaps: no general stock/ETF quotes, no forex/commodities data, and no cross-country aggregate search. The mix of scrapers and alerts leaves the surface feeling uneven.

Resources