listing

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:

fill out their property's information,
set a price,
choose a package and any add-ons,
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

Name	Required	Description
`package`	No	Page preset index 1-4: 1=Basic $99, 2=Enhanced $399, 3=Concierge $999, 4=Basic+Title $199. NOT a payPremiumOpt reference.
`access_token`	Yes	Bearer access token from beycome_signin_verify, or a previously saved token from your memory for this user.
`list_address`	No	Full property address to prefill the page (the address discussed in chat).

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.9/5.0

Behavior5/5

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

No annotations exist, so the description fully discloses behavior: it returns a pre-authorized URL expiring in 7 days, the listing is created in the browser, and failure modes (401 for bad tokens) are listed. It also warns about the package parameter being a preset index, not a payPremiumOpt reference.

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?

The description is detailed but well-structured, with key information front-loaded (purpose, prerequisites). It uses clear paragraphs and warning notes. While slightly lengthy, every sentence adds value for a complex tool, so it is appropriately sized.

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?

Given the tool's complexity and that an output schema exists, the description covers all necessary aspects: workflow, parameter details, failure modes, post-call actions, and even script for the agent. It is fully complete for an AI agent to use correctly.

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?

Schema coverage is 100%, but the description adds significant value: for 'package', it explains the mapping from index to price and warns against misuse; for 'list_address', it advises to always pass it; for 'access_token', it specifies the source. This exceeds what the schema alone provides.

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 clearly states the tool's purpose: 'mint a pre-authorized link to the submit-property page' for listing creation. It distinguishes itself from siblings by noting it's the only way to create a listing and directs the agent to subsequent tools like beycome_get_my_listings and beycome_questionnaire_link.

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?

The description explicitly tells when to use the tool: 'Call AFTER signing in (beycome_signin_verify).' It provides a complete workflow: call this, present the link, user fills out, then call beycome_get_my_listings. It also states there is no in-chat alternative, giving clear usage context.

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

All listing 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.4/5.0

Disambiguation5/5

Each tool targets a distinct stage or action in the listing workflow: discovery, account, creation, questionnaire, and post-publish. There is no functional overlap—even pricing-adjacent tools like comps and estimate are clearly differentiated by their outputs.

Naming Consistency4/5

All tools share the 'beycome_' prefix and lowercase underscores, but some are verbs (submit_property_link) while others are nouns (comps, offers). This minor inconsistency does not impair readability or agent selection.

Tool Count5/5

14 tools cover the full lifecycle of a real estate listing without feeling bloated or sparse. Each tool has a clear role, making the set well-scoped for the domain.

Completeness4/5

Core CRUD and lifecycle operations are present, including discovery, sign-up, listing creation, and post-publish communication. Missing are tools for updating or deleting a live listing, but the main workflow is supported.

Resources

Need Help?