listing

beycome_questionnaire_link

Questionnaire stage — mint a pre-authorized link to the MLS questionnaire form (POST /api/mls/questionnaire-link).

Requires a PAID listing (premium active, Flat/Yes) — whether the user just paid on the submit-property page (beycome_submit_property_link) or already had a paid listing with the questionnaire still pending. Returns a pre-authorized link (expires in 7 days) — this tool only hands back the URL; everything else happens in the browser, with no login step. Present the URL and tell the user that on the page they will:

review the pre-filled MLS questionnaire and complete any fields Beycome couldn't pre-fill,
upload property photos and the required documents,
review and submit. After they submit, the listing goes live within about 48 hours, provided all the paperwork clears.

Failure modes to relay plainly: 403 — the token is not the owner's; 422 — the listing is not paid yet, or the questionnaire was already submitted; 401 — bad/missing token.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`prop_id`	Yes	Property id in beycome.
`access_token`	Yes	Bearer access token from beycome_signin_verify, or a previously saved token from your memory for this user.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.8/5.0

Behavior5/5

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

No annotations provided, but description fully discloses behavior: returns an expiring link, no login step, browser actions required, 48-hour processing. No contradictions with missing annotations.

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?

Well-structured with clear sections (prerequisites, workflow, failure modes). Slightly verbose but each sentence contributes to clarity; could be tightened slightly.

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?

Covers all aspects: purpose, prerequisites, return value, user actions, timeline, and error handling. No gaps given lack of annotations and presence of output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds value by specifying the source of access_token (from beycome_signin_verify or saved token), enhancing parameter understanding beyond 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 clearly states the verb ('mint'), resource ('pre-authorized link to the MLS questionnaire form'), and method (POST). It distinguishes from sibling tools like beycome_submit_property_link by specifying context.

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?

Explicitly states prerequisites (PAID listing, premium active, Flat/Yes) and failure modes (403, 422, 401). References related tool (beycome_submit_property_link) and explains when to use.

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?