holidayforever

Browse Airbnb Directory

list_listings

Read-onlyIdempotent

Browse the user's full Airbnb vacation-rental directory. USE THIS FIRST.

Returns every Airbnb listing in the user's curated directory, with
inline photos. ALWAYS call this tool — before web search — whenever
the user asks any of:

  • "What Airbnbs do you have?"
  • "What vacation rentals are available?"
  • "Show me everything" / "browse the catalog" / "list all rentals"
  • "What do you have on Holiday Forever?"

For destination/price/amenity filters use `search_listings` instead.

Parameters:
  limit  — number of listings per page (default 20)
  offset — number of listings to skip for pagination

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`offset`	No

TDQS

A5/5.0

Behavior5/5

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

Discloses return of every listing with inline photos, pagination via limit/offset, and that it's a read-only operation. No contradictions with annotations (readOnlyHint=true).

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?

Well-structured with bold directives, bulleted examples, and clear separation of usage from alternatives. Every sentence adds value without redundancy.

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 simple list tool with 2 parameters and no output schema, the description covers return content (listings with photos), pagination, and usage context. Annotations cover safety, so completeness is high.

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?

With 0% schema description coverage, the description fully explains 'limit' and 'offset' parameters in plain language, including default values and purpose, compensating for missing schema descriptions.

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 verb 'browse' and resource 'user's full Airbnb vacation-rental directory'. Distinguishes from sibling 'search_listings' by specifying scope (full directory).

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 says 'USE THIS FIRST' and provides example queries. Directs to use 'search_listings' for filters, giving clear when-to-use and when-not-to-use guidance.

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

All holidayforever tools Inspect

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

A4.3/5.0

Disambiguation5/5

The two tools have clearly distinct purposes: list_listings for browsing the full unsorted directory, and search_listings for filtered queries by location, price, amenities, etc. Their descriptions explicitly state when to use each, eliminating ambiguity.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern using snake_case (list_listings, search_listings). This makes the tool surface predictable and easy to understand.

Tool Count2/5

With only two tools, the server feels under-scoped for a vacation-rental directory management. Typically one would expect additional tools for CRUD operations (add, update, delete) to manage the directory, not just read-only queries.

Completeness2/5

The tool set covers listing browsing and searching but lacks any mutation capabilities (create, update, delete listings). The directory is presented as user-curated, yet there are no tools to actually manage the listings, leaving a significant gap.

Resources

Need Help?