listing

beycome_messages

Post-publish stage — read the owner's buyer/inquiry messages (GET /messages).

Read-only. Requires access_token. Two modes:

Omit thread → lists the ~20 most recent conversations, newest first, one row per thread (the latest message in each). Useful fields per row: address, prop_id, prop_status, msg (latest text), subject, requested_by / email (the other party), thread, read_msg ("0" = unread), attachments, and message_type (sender if the owner wrote the latest message, else receiver).
Pass thread → returns that one conversation in full, oldest-first. Use the thread value from a list row to drill in.

The list is not paginated here on purpose (the upstream page param is overloaded — it sets both page size and page number — so it is not exposed). Soft-deleted messages are dropped after paging, so a page may hold fewer than 20 rows; that is not an error. The payload is a bare array under data.

A 401 means the token is no longer valid (logged out, or very old) — re-authenticate with beycome_signin_start then beycome_signin_verify. To answer a message, use beycome_reply_message.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`thread`	No	Thread id to open one full conversation (the ``thread`` value from a list row). Omit to list the user's recent conversations.
`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, so description covers all behavioral aspects: read-only, token requirement, list non-pagination rationale, soft-deleted message behavior, response structure (bare array under `data`), and 401 error handling. Very transparent.

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 fairly long but well-structured, front-loading the main purpose. It includes some minor extraneous detail (e.g., field list), but these are helpful for the agent. Could be slightly more concise but still efficient.

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?

Despite having an output schema, the description covers return structure, error handling, authentication flow, and links to sibling tools. The agent has all necessary context to use the tool correctly.

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 value by explaining the effect of omitting vs passing `thread`, the source of `access_token`, and the fields in list rows. This goes beyond the schema's basic descriptions.

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 reads owner's buyer/inquiry messages (GET /messages). It distinguishes two modes (list vs thread) and differentiates from sibling tool `beycome_reply_message` for replying. The verb 'read' and resource 'messages' are specific and unambiguous.

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 explains when to omit or pass `thread`, and directs users to `beycome_reply_message` for answering messages. Also guides re-authentication on 401. Provides clear context for using this tool over alternatives.

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?