Skip to main content
Glama

Get create-listing link

beycome_submit_property_link

Listing-creation stage — mint a pre-authorized link to the submit-property page (POST /api/mls/submit-property-link).

Call AFTER signing in (beycome_signin_verify). User-scoped — no prop_id exists yet. Returns a pre-authorized link (expires in 7 days) — this tool only hands back the URL; the listing is created in the browser, with no login step. Present the URL and tell the user that on the page they will:

  1. fill out their property's information,

  2. set a price,

  3. choose a package and any add-ons,

  4. pay. Tell them to return to the chat once payment is complete.

Prefill: the page accepts prefill params baked into the signed URL.

  • list_address: the full property address. By this stage the user has already told Claude their address (discovery ran on it), so ALWAYS pass list_address so the page opens pre-filled.

  • package: the page PRESET INDEX (1-4), not a payment reference — 1 = Basic $99 2 = Enhanced $399 3 = Concierge $999 4 = Basic + Title $199 WARNING: this is the page preset index, NOT an internal payPremiumOpt reference number. Passing a payPremiumOpt reference here is wrong. Only pass package if the user has clearly chosen a tier in chat; otherwise omit it and let them pick on the page.

Failure modes to relay plainly: 401 — bad/unverified token.

This page is THE way to create a listing — the property is created, priced, and paid for there; there is no in-chat alternative. After the user returns, call beycome_get_my_listings to recover the new prop_id, then beycome_questionnaire_link.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packageNoPage preset index 1-4: 1=Basic $99, 2=Enhanced $399, 3=Concierge $999, 4=Basic+Title $199. NOT a payPremiumOpt reference.
access_tokenYesBearer access token from beycome_signin_verify, or a previously saved token from your memory for this user.
list_addressNoFull property address to prefill the page (the address discussed in chat).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / access_token / description
      Previous value: -"Bearer access token from beycome_signin_verify."New value: +"Bearer access token from beycome_signin_verify, or a previously saved token from your memory for this user."
  2. Changed1 schema field changed
    • changedInput schema / properties / access_token / description
      Previous value: -"Bearer access token from beycome_signin."New value: +"Bearer access token from beycome_signin_verify."
  3. Added

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources