SiteCheck Jobs & Property

LoopNet commercial real estate listings for a US city

realestate_loopnet

Read-only

LoopNet commercial real estate listings for a US city: listing id, address, building name, property type (office, retail, industrial, land, multifamily...), listing type, price or rent text, size, unit count and other card facts, short blurb, broker and brokerage, ZIP and link; for sale or for lease, page 1 to 20. From loopnet.com's public search pages through a proxy. Related tools on this server, for a different need: realestate_immowelt when you need German property listings from immowelt.de for a city: per; realestate_realtytrac when you need RealtyTrac foreclosure listings for a US city or ZIP. Price: $0.01 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "city": "<city>",
      "state": "<state>"
    },
    "name": "realestate_loopnet"
  }
}

Input Schema

Name	Required	Description
`city`	Yes	City name, e.g. austin
`deal`	No	for-sale or for-lease (default for-sale)
`page`	No	Results page 1 to 20 (default 1)
`state`	Yes	Two-letter US state code, e.g. tx
`propertyType`	No	commercial-real-estate (all), office-space, retail-space, industrial-properties, land, multifamily (default commercial-real-estate)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The annotations already declare readOnlyHint and openWorldHint, while the description adds source details (public LoopNet search pages through a proxy), pagination bounds, and x402 payment behavior with failed calls not charged. It does not describe rate limits or response shape, though 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?

The definition is mostly front-loaded, with field list, scope, alternatives, and pricing each earning space. However, the related-tools sentence is a dense run-on and the 'for a city: per;' fragment is unclear.

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?

For a five-parameter, read-only scraping tool, the description covers source, geography, returned fields, pagination, alternatives, and payment. With an output schema handling return details, nothing critical is missing for correct invocation.

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 description coverage is 100% and all five parameters have descriptions, including defaults and property-type options. The prose restates city/state/page/deal/property type rather than adding new format or constraint details beyond the schema, so the 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?

The opening clause names the source (LoopNet), resource (commercial real estate listings), and scope (US city), then enumerates the returned fields. It explicitly distinguishes itself from realestate_immowelt for German listings and realestate_realtytrac for foreclosure listings.

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?

It gives clear context for use: LoopNet commercial listings in a US city, with for-sale/for-lease and page 1-20 scope. It names two sibling tools for different needs, but does not explicitly exclude other US commercial listing tools or state a when-not condition.

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

All SiteCheck Jobs & Property tools Inspect

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

Need Help?