Skip to main content
Glama

Tu Lugar

by com.tulugar

Create Listing

create_listing

Create a real estate listing for the authenticated agent. Always creates a private DRAFT — it is NOT visible publicly. A city or neighborhood is enough to start; NEVER invent coordinates (fabricated pins are discarded). The response returns an edit-page link with a map: ask the user to open it and drop the pin on the exact property location, and wait for their confirmation before publish_listing — publishing is blocked until a human sets the pin and at least one photo. Requires a CONNECTED account with a verified WhatsApp number — if unsure, call account_status FIRST and, if not connected, share the connect steps it returns instead of attempting to create.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imagesNoUp to 25 image URLs. Optional for a draft; at least one is required to publish.
locationYesListing location. The country/market is inferred from the city and coordinates — use real place names so it resolves correctly (e.g. Asunción → Paraguay, Montevideo → Uruguay, Buenos Aires → Argentina, Curitiba → Brazil). For a draft, a city or neighborhood is enough; the owner sets the exact pin on the web. Provide latitude/longitude ONLY if you have precise coordinates — never guess them.
descriptionNo
land_detailsNoBedrooms/bathrooms/area for the property.
listing_typeYes
price_amountYesPrice (positive number)
house_detailsNoBedrooms/bathrooms/area for the property.
property_typeYes
price_currencyNoUse the currency local to the market (e.g. PYG in Paraguay, UYU or USD in Uruguay, ARS in Argentina, BRL in Brazil). Defaults to PYG if omitted.
source_languageYesLanguage the title/description are written in
apartment_detailsNoBedrooms/bathrooms/area for the property.
commercial_detailsNoBedrooms/bathrooms/area for the property.

TDQS

A4.8/5.0
Behavior5/5

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

Discloses that listing is private draft, not public; warns against inventing coordinates; clarifies that publishing is blocked until pin and photo; notes country inference from city/coordinates; no contradiction with annotations.

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?

Well-structured and front-loaded, but slightly verbose with repeated property detail descriptions across multiple objects; still efficient for the tool's complexity.

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?

Covers purpose, workflow, prerequisites, parameter guidance, and return format (edit-page link); missing some error details, but adequate given no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds meaning beyond schema: explains what parameters are optional for draft vs required for publish, advises on location precision, source_language usage, and currency locale.

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?

Clearly states 'Create a real estate listing for the authenticated agent' and specifies it always creates a private draft, distinct from publish_listing and other siblings.

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

Usage Guidelines5/5

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

Explicitly explains when to use: creates draft; prerequisites (connected account, verified WhatsApp); advises calling account_status first; instructs to ask user to drop pin and wait before publish_listing.

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

All Tu Lugar 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

A3.7/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, but there is some overlap between 'search' and 'search_listings', and between 'fetch' and 'get_listing'. However, descriptions effectively differentiate them.

Naming Consistency3/5

Naming follows multiple patterns: verb_noun (create_listing), noun (closing_costs), get_*, search_*, my_*. While each pattern is internally consistent, the mix reduces overall consistency.

Tool Count3/5

39 tools is relatively high, but they cover a broad set of real estate functionalities. The count feels slightly heavy but is justified by the domain scope.

Completeness5/5

The tool set covers the full lifecycle of listings (CRUD, promotion, sharing), account management, search with multiple filters, market data, guides, and lead management. No obvious gaps for the platform's purpose.

Resources