Skip to main content
Glama

Look up a listing link

lookup_by_url
Read-onlyIdempotent

Resolve a listing link (Airbnb, Booking, Vrbo) to the operator's Ospitario passport, e.g. when a traveler wants to book a place they know directly. Exact match on the listing's own L2/L2c proof or found:false; never a list; a property verified only as an operator (L3) or an unclaimed passport (L0) is never returned for a link. The link is only parsed, never opened. Insurance status and safety equipment are host-declared, not verified: Ospitario has seen no policy and no device. Every result is a property with a proven listing (L2/L2c), a verified operator (L3), a right to manage verified by document review (LA) or, marked L0 and unclaimed, facts from the operator's official website with nothing proven; the result names the tier and the date it was reached, and whether the registration number (Italy: CIN) was checked against the public register. Contact is direct with the operator and commission-free, so the traveler pays no platform fee. No result means nothing proven matches; nothing is inferred, estimated or filled 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": "lookup_by_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesLink to a listing on Airbnb, Booking or Vrbo
langNoLanguage of labels in the result; defaults to en

Output Schema

NameRequiredDescriptionDefault
foundYes
reasonNonot_found: no operator holds a listing-control proof (L2/L2c) on this listing; unsupported_url: not a listing link Ospitario understands
propertyNo
contactPageUrlNoPage with the passport and the operator's direct contact; give this link to the traveler

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changed
    • addedOutput schema / properties / property / properties / facilities / properties / balcony
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / property / properties / facilities / properties / bbq
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "A barbecue or outdoor grill"
      +}
    • addedOutput schema / properties / property / properties / facilities / properties / crib
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "A cot for a baby"
      +}
    • addedOutput schema / properties / property / properties / facilities / properties / elevator
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / property / properties / facilities / properties / fireplace
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / property / properties / facilities / properties / hotTub
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / property / properties / facilities / properties / kitchen
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / property / properties / facilities / properties / microwave
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / property / properties / facilities / properties / tv
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / property / properties / facilities / properties / washingMachine
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / property / properties / facilities / properties / wifi
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • changedOutput schema / properties / property / properties / facilities / required
      Previous value: -[
      -  "parking",
      -  "workspace",
      -  "airConditioning",
      -  "heating"
      -]New value: +[
      +  "parking",
      +  "workspace",
      +  "airConditioning",
      +  "heating",
      +  "wifi",
      +  "kitchen",
      +  "washingMachine",
      +  "tv",
      +  "bbq",
      +  "crib",
      +  "elevator",
      +  "hotTub",
      +  "fireplace",
      +  "balcony",
      +  "microwave"
      +]
    • addedOutput schema / properties / property / properties / floorArea
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Living area in square metres as the operator states it; null: not stated"
      +}
    • changedOutput schema / properties / property / required
      Previous value: -[
      -  "slug",
      -  "name",
      -  "municipality",
      -  "province",
      -  "country",
      -  "type",
      -  "capacity",
      -  "bedrooms",
      -  "amenities",
      -  "pool",
      -  "placeKind",
      -  "bathrooms",
      -  "petsAllowed",
      -  "checkinFrom",
      -  "checkoutUntil",
      -  "location",
      -  "minNights",
      -  "beds",
      -  "extraCosts",
      -  "childrenAllowed",
      -  "stepFreeAccess",
      -  "unitCount",
      -  "propertyKind",
      -  "smokingAllowed",
      -  "eventsAllowed",
      -  "cleaningFee",
      -  "securityDeposit",
      -  "facilities",
      -  "description",
      -  "locationNotes",
      -  "houseRules",
      -  "cancellation",
      -  "contact",
      -  "verification",
      -  "registration",
      -  "references",
      -  "availability",
      -  "blocked",
      -  "liabilityInsurance",
      -  "priceFrom",
      -  "unclaimed",
      -  "summary",
      -  "languages",
      -  "safety",
      -  "safetyStated",
      -  "trust",
      -  "provenance",
      -  "booking"
      -]New value: +[
      +  "slug",
      +  "name",
      +  "municipality",
      +  "province",
      +  "country",
      +  "type",
      +  "capacity",
      +  "bedrooms",
      +  "amenities",
      +  "pool",
      +  "placeKind",
      +  "bathrooms",
      +  "floorArea",
      +  "petsAllowed",
      +  "checkinFrom",
      +  "checkoutUntil",
      +  "location",
      +  "minNights",
      +  "beds",
      +  "extraCosts",
      +  "childrenAllowed",
      +  "stepFreeAccess",
      +  "unitCount",
      +  "propertyKind",
      +  "smokingAllowed",
      +  "eventsAllowed",
      +  "cleaningFee",
      +  "securityDeposit",
      +  "facilities",
      +  "description",
      +  "locationNotes",
      +  "houseRules",
      +  "cancellation",
      +  "contact",
      +  "verification",
      +  "registration",
      +  "references",
      +  "availability",
      +  "blocked",
      +  "liabilityInsurance",
      +  "priceFrom",
      +  "unclaimed",
      +  "summary",
      +  "languages",
      +  "safety",
      +  "safetyStated",
      +  "trust",
      +  "provenance",
      +  "booking"
      +]
  2. Changed1 schema field changed
    • changedOutput schema / properties / property / properties / verification / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "date": {
      -        "description": "Date the tier was reached, YYYY-MM-DD",
      -        "type": "string"
      -      },
      -      "label": {
      -        "description": "Human-readable name of the tier",
      -        "type": "string"
      -      },
      -      "tier": {
      -        "description": "Verification tier (docs: ADR 0012, 0017, 0024, 0025). L0 unclaimed: facts read from the operator's official website, nothing proven, the operator has not claimed the page; contact only through send_inquiry. L2 listing verified: the operator proved control of the platform listing (calendar export link with the listing id, platform email with a valid DKIM signature, or channel manager); since 2026-11-07 also their right to manage the property (LA or L3), and earlier L2 stands as it was reached. L2c listing calendar proven (Booking, Vrbo): the operator blocked a random date Ospitario named in that platform's calendar export within 48 hours; no new L2c since 2026-11-07. LA right to manage verified (document review): Ospitario's admin checked documents tying the operator to this property (registration record, deed, lease, mandate or company register); a person found them consistent, without eID, so it does not prove who holds the account and never proves a platform listing. L3 operator verified: the operator's eID identity (SPID/CIE) matches the CIN holder in the national register's PDF. L4 document verified (automated check): an ownership, lease or mandate document is consistent with that identity and the property; it states consistency, not authenticity. L5 manually verified: a reviewer checked the document (an optional upgrade; it does not affect search order).",
      -        "enum": [
      -          "L0",
      -          "L2",
      -          "L2c",
      -          "LA",
      -          "L3",
      -          "L4",
      -          "L5"
      -        ],
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "tier",
      -      "label",
      -      "date"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "date": {
      +        "description": "Date the tier was reached, YYYY-MM-DD",
      +        "type": "string"
      +      },
      +      "label": {
      +        "description": "Human-readable name of the tier",
      +        "type": "string"
      +      },
      +      "tier": {
      +        "description": "Verification tier (docs: ADR 0012, 0017, 0024, 0025). L0 unclaimed: facts read from the operator's official website, nothing proven, the operator has not claimed the page; contact only through send_inquiry. L2 listing verified: the operator proved control of the platform listing (calendar export link with the listing id, platform email with a valid DKIM signature, or channel manager); since 2026-11-07 also their right to manage the property (LA or L3), and earlier L2 stands as it was reached. L2c listing calendar proven (Booking, Vrbo): the operator blocked a random date Ospitario named in that platform's calendar export within 48 hours; no new L2c since 2026-11-07. LA right-to-manage documents reviewed: Ospitario's admin checked documents tying the operator to this property (registration record, deed, lease, mandate or company register); a person found them consistent, without eID, so it does not prove who holds the account and never proves a platform listing. L3 operator verified: the operator's eID identity (SPID/CIE) matches the CIN holder in the national register's PDF. L4 document verified (automated check): an ownership, lease or mandate document is consistent with that identity and the property; it states consistency, not authenticity. L5 manually verified: a reviewer checked the document (an optional upgrade; it does not affect search order).",
      +        "enum": [
      +          "L0",
      +          "L2",
      +          "L2c",
      +          "LA",
      +          "L3",
      +          "L4",
      +          "L5"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "tier",
      +      "label",
      +      "date"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  3. Changed2 schema fields changed
    • changedOutput schema / properties / property / properties / checkoutUntil / description
      Previous value: -"Checkout until, HH:MM local time; null: not stated"New value: +"Checkout until, HH:MM local time; null: not stated (a stated 00:00, usually 12:00 AM typed for noon, counts as not stated)"
    • changedOutput schema / properties / property / properties / extraCosts / description
      Previous value: -"Costs beyond the nightly price in the operator's words (cleaning, tourist tax, linen, energy); null: not stated, which is not the same as none"New value: +"Costs beyond the nightly price in the operator's words (cleaning, tourist tax, linen, energy); null: not stated, which is not the same as none (a bare number without what or currency counts as not stated)"
  4. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations, the description discloses exact-match behavior, what qualifies for a result, what is never returned, that the link is parsed but never opened, which facts are host-declared rather than verified, and that results include tier and date information.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the description is very long for a two-parameter lookup tool and includes dense, semicolon-heavy tier explanations plus commercial details such as commission-free contact. Some tier caveats are relevant, but the overall text is not tightly edited.

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 domain-specific lookup with an output schema, the description supplies the necessary conceptual context: exact-match resolution, tier meanings, unclaimed and operator-only exclusions, and verification caveats. An agent has enough information to call it correctly and interpret the result model.

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%, so both parameters are already documented in the schema. The description adds that the URL is parsed but never opened, but it does not further explain the language parameter, so this sits at the baseline for a well-covered schema.

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?

The description gives a specific verb and resource: 'Resolve a listing link (Airbnb, Booking, Vrbo) to the operator's Ospitario passport.' It also states that the result is exact-match or found:false and 'never a list,' which distinguishes it from list/search tools.

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 provides a clear usage context: 'when a traveler wants to book a place they know directly,' and explicitly rules out list-style results. It does not explicitly mention the sibling lookup_by_name as the alternative when only a name is available, so the routing guidance is strong but not exhaustive.

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