Skip to main content
Glama

OwnerRez MCP by usefulapi

by io.usefulapi
OverviewDiscussionsAdmin

List bookings

list_bookings
Read-only

List bookings (reservations). OwnerRez API: GET /v2/bookings. Filter by property, date range, changed-since, and status; opt into embedded charges/guest/tags. Returns { items, count, limit, offset, next_page_url }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoEnd of the arrival/stay date window (ISO-8601).
fromNoStart of the arrival/stay date window (ISO-8601, e.g. 2026-07-01).
limitNoMax items to return per page (default set by OwnerRez, typically 10).
offsetNoNumber of items to skip (for paging; combine with limit).
paramsNoAdditional documented query-string filters to send verbatim (merged with the typed params above).
statusNoFilter by booking status.
since_utcNoOnly bookings created/updated on or after this UTC timestamp (ISO-8601).
include_tagsNoInclude the tags collection on each booking.
property_idsNoComma-separated property id(s) to filter by, e.g. "123" or "123,456".
include_guestNoInclude the embedded guest object on each booking.
include_fieldsNoInclude the custom-fields collection on each booking.
include_chargesNoInclude the charges breakdown on each booking.
include_cancellation_policyNoInclude the cancellation-policy detail.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / properties / params / additionalProperties / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  }
-]
    • addedInput schema / properties / params / additionalProperties / type
      Added value: +[
+  "string",
+  "number",
+  "boolean"
+]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

readOnlyHint=true already establishes the safety profile, and the description adds real context beyond it: the upstream endpoint, the opt-in embedding flags, and the pagination envelope ({ items, count, limit, offset, next_page_url }). It stops short of stating rate limits, default page size behavior beyond the schema, or ordering guarantees.

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?

Three short sentences, no filler, with the resource and endpoint front-loaded and the return shape last. Slightly dense with category lists, but nothing is wasted.

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 13-param read-only list tool with no output schema, the description covers the filter surface, the pagination model, and the response envelope, which compensates for the missing output schema; annotations cover the safety profile. An agent has everything needed to invoke it correctly.

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%, so every parameter, including the free-form 'params' escape hatch and the include_* flags, is already documented in structured data. The description's summary of filter axes restates that surface rather than adding syntax or edge-case meaning, so the baseline 3 applies.

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+resource ('List bookings (reservations)'), pins the underlying OwnerRez endpoint (GET /v2/bookings), and enumerates the filter axes and embedded expansions. An agent can distinguish this from get_booking or list_inquiries without opening the schema.

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 when the tool is useful (filtering bookings by property, date window, changed-since, status) but never states when to prefer it over siblings such as get_booking for a single record or list_inquiries. Usage is inferable rather than directed.

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

All OwnerRez MCP by usefulapi toolsInspect
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