Skip to main content
Glama

Guest2Host

Apply to list a rental

apply_to_list

For owners: apply to list a vacation rental on Guest2Host (free, no commission, never takes payments). Needs four things: the property name, its town and state, the owner's own booking-site link and the owner's email. The owner gets a confirmation email with a status link (also returned here); once the Guest2Host team approves it (usually within a business day) the listing is built from their booking site and put live, and they are emailed the link — a sign-in only if they want to edit it. Use only with the owner's agreement.

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": {
      "ownerEmail": "<ownerEmail>",
      "propertyName": "<propertyName>",
      "location": "<location>"
    },
    "name": "apply_to_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNo
sleepsNoOptional
vrboUrlNo
locationYesTown and state, e.g. "Leavenworth, WA"
airbnbUrlNo
ownerNameNoOptional
ownerEmailYesWhere the confirmation and the sign-in invite go
propertyNameYese.g. "Riverbend Cabin"
propertyTypeNoOptional
wantsSiteBuildNoNo booking site yet and would like Guest2Host to build one (paid)
directBookingUrlNoThe owner's own booking site (https) — the page for this home if there is one. Required unless wantsSiteBuild is true

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare non-read-only, non-destructive, non-idempotent and open-world, and the description adds genuinely new behavior: free, no commission, never handles payments, a confirmation email with a status link that is also returned here, team approval typically within a business day, and a sign-in only needed to edit. What it omits is the failure/duplicate-submission path, which matters for a non-idempotent apply.

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?

It is a single dense paragraph but front-loads the audience, the action and the inputs before the lifecycle detail. No filler sentences, though the length pushes the practical constraint (the consent requirement) to the very end where it is easy to miss.

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 an 11-parameter, no-output-schema submission tool, the description supplies the missing lifecycle context: what the owner receives, the approval timeline, how the listing is generated, and what is returned here (the status link). Combined with 73% schema coverage, an agent has everything needed to submit responsibly.

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?

It highlights the four key inputs (property name, town/state, booking-site link, owner email) and explains the email's role as the destination for confirmation and sign-in invite. However, it presents the booking-site link as always required while the schema says it is only required unless wantsSiteBuild is true, and it never mentions the optional inputs (sleeps, notes, propertyType, vrboUrl/airbnbUrl) that could improve the listing.

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?

"For owners: apply to list a vacation rental on Guest2Host" gives a specific audience, verb and resource in one clause. None of the siblings (search_stays, check_dates, send_inquiry, etc.) do anything similar, so the agent can route to it without inspecting other schemas.

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 names the actor (the owner) and adds a real precondition: "Use only with the owner's agreement." It does not compare against alternatives or state when-not to call, but the surrounding siblings are unrelated discovery/booking tools, so the implied usage is unambiguous.

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.

Resources