Skip to main content
Glama

Find the listings on my website

find_listings_on_website
Read-onlyIdempotent

List the property listing pages on a seller's own website (url: the site, or the page that lists their properties), so they can be added to Fabrica (Sepolia Testnet) one by one with add_land (listingUrl). The site is read from its sitemap or its links; nothing is created or changed. Returns the site, each listing's link (up to 200) and whether the list was cut short. Only for the person's own listings on their own website: add_land copies each listing's description and photos. Needs the person to be signed in.

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": {
      "url": "<url>"
    },
    "name": "find_listings_on_website"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe seller's website, or the page that lists their properties (e.g. 'example-land.com/properties')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld/idempotent annotations: discloses that the site is crawled via sitemap or links, that nothing is created or changed, that results cap at 200 with a truncation flag, and that the caller must be signed in. That is exactly the behavioral context an agent needs before invoking it.

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?

Purpose is front-loaded in the first clause, then mechanism, return shape, eligibility, and auth follow in a logical order. It is dense and slightly long, but no sentence 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?

With no output schema, the description still explains what comes back (site, each listing link, truncation flag), the 200-item limit, the auth requirement, and how results feed add_land. Nothing an agent needs to call it correctly is missing.

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 coverage is 100% and the schema already explains that url is the site or the page that lists properties; the description largely repeats this rather than adding new syntax or formatting guidance. Baseline 3 is appropriate when the schema carries the parameter burden.

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 — listing the property listing pages on a seller's own website — and ties it to a concrete downstream action (adding to Fabrica with add_land). The scope ('own website') distinguishes it from parcel-lookup siblings like find_us_parcel.

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?

Explicitly bounds usage to 'the person's own listings on their own website' and frames the follow-up workflow with add_land (listingUrl). It does not name what to use for other listing sources, so it stops just short of full when/when-not routing.

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.