listing

beycome_signin_verify

Account stage — exchange the one-time code for the access_token (POST /auth/validate-code).

The gateway to the listing flow. Call after beycome_signin_start or beycome_signup (both send the code) with the 6-digit code the user received. On success the Bearer token is at data.data.access_token (expires_in gives its lifetime in seconds — tokens are long-lived, so mid-session expiry is rare). Pass it as access_token to every authenticated tool: beycome_submit_property_link, beycome_get_my_listings, beycome_questionnaire_link, beycome_offers, beycome_showings, beycome_messages, and beycome_reply_message.

IMPORTANT — persist the token: save the access_token to your long-term memory/context (and tell the user you have done so). Save it together with the account email, which disambiguates multi-account users and lets you match the right token to the right person. In future sessions, scheduled tasks, and crons, reuse the saved token instead of asking the user to sign in again — that is what makes autonomous workflows (e.g. "check my messages every morning") possible. Before signing a user in, check your memory for an existing token for that email and try it first; only restart the sign-in flow on a 401.

The next step depends on where the user is:

No listing yet → beycome_submit_property_link to create one.
Has a listing already (or unsure) → beycome_get_my_listings to find it; if it is paid but the MLS questionnaire is not submitted, follow with beycome_questionnaire_link.
Listing already live → skip straight to the post-publish tools (beycome_messages, beycome_showings, beycome_offers).

A wrong or expired code returns HTTP 200 with success: false and "Invalid code." — check data.success, not the envelope's ok. Codes expire after 30 minutes; if expired, request a fresh one with beycome_signin_start (don't retry blindly — sends are rate-limited).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`code`	Yes	6-digit one-time code the user received by email or SMS.
`email`	Yes	User email address.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.6/5.0

Behavior4/5

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

No annotations provided, so description carries full burden. Discloses key behaviors: token long-lived, response success field is data.success, code expires in 30 minutes, and imperative to persist token. Lacks explicit statement about side effects but given authentication context, it's adequate.

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?

Description is relatively long but well-organized with clear sections. Front-loaded with core purpose and followed by usage details. Every sentence adds value; no filler.

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 output schema exists, description properly explains return fields (access_token, expires_in) and error handling. Also covers token persistence, multi-account disambiguation, and session reuse. Thoroughly completes the context for the tool's role in the authentication flow.

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%, baseline 3. Description adds meaning by specifying code is 6-digit and obtained via email/SMS, and mentions 30-minute expiry, which is valuable context beyond the schema fields.

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?

Clearly states the tool exchanges a one-time code for an access token, and positions it as the gateway to the listing flow. Distinguishes from siblings like beycome_signin_start and beycome_signup by specifying it is called after those.

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 says when to call (after signin_start or signup), what input to provide (6-digit code), and how to handle errors (wrong/expired code). Gives detailed next steps based on user state and warns about rate limits on retries.

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?