listing

beycome_get_my_listings

Recovery stage — the signed-in user's properties (GET /properties).

Token-scoped RESO list endpoint on the normal api base. Two main uses:

After the user finishes the submit-property page (beycome_submit_property_link): find the newly created listing (typically the newest entry), CONFIRM the address with the user, then use its id as prop_id for beycome_questionnaire_link.
As the entry point for a returning user who already has listings (or references "my listing" without an id): locate the listing and read its status to pick the next step — paid but questionnaire pending → beycome_questionnaire_link; already live → the post-publish tools (beycome_messages, beycome_showings, beycome_offers).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`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.3/5.0

Behavior3/5

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

With no annotations, the description carries full behavioral burden. It states it's a token-scoped RESO list endpoint, implying read-only listing. However, it does not disclose potential edge cases (e.g., empty list, invalid token, pagination) or side effects, leaving some behavior uncovered.

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 concise with front-loaded purpose and clear use cases. A slight lack of structure (block text instead of bullets) but every sentence adds value, with no redundant phrasing.

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 complex workflow with many sibling tools, the description fully orients the agent by detailing integration points (after submission, for returning users) and linking to downstream tools. Output schema exists to cover return details, so no gap.

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?

The only parameter, access_token, is described with specific provenance (from beycome_signin_verify or saved token), adding critical context beyond the schema's description. This helps the agent correctly provide the token.

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 retrieves the signed-in user's listings (GET /properties) and differentiates from siblings by specifying two main use cases: after property submission to find new listing, and for returning users to locate listings. This directly distinguishes it from tools like beycome_submit_property_link 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit scenarios for when to use the tool (after submission, for returning users) and references sibling tools for next steps (questionnaire_link, messages, showings, offers). Lacks explicit when-not-to-use guidance, but the context is clear enough for appropriate selection.

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?