Landlord Bench

Read your listings

my_listings

Read-onlyIdempotent

What the Landlord Bench owner dashboard shows about the listings an account owns: each one's status (status.kind: review with the expected date, accepted with liveOn and paid ('express' | 'featured' | null: the paid way that releases it, Featured including VIP listing), live, refused with the reason, or archived), the listing as it shows, where AI answers named the product or cited its page, and what it can buy here at this site's prices. Only for the account itself: send its session Cookie header, or its agent key with "Read your listings" as Authorization: Bearer. Same answer as GET https://landlordbench.com/api/owner/listings. Read-only: corrections go through the dashboard's request form.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "my_listings"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	No	Optional: one listing, by its slug. Without it, every listing the account owns.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the description's main added value is the authentication requirement (session Cookie header or agent key as Bearer) and the equivalence to GET https://landlordbench.com/api/owner/listings. It also restates read-only with a redirect to the dashboard request form, which is useful routing context beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single dense parenthetical-heavy paragraph that front-loads return-field detail ahead of the authentication requirement, which is arguably the more actionable information for calling the tool. Phrases such as 'the listing as it shows' and 'what it can buy here at this site's prices' are vague and consume space without resolving meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of describing return values and does so in reasonable detail: status kinds, liveOn/paid values, refusal reasons, AI citation info. The auth path and endpoint equivalence round it out. Some return fields remain loosely specified, so it is not fully complete.

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

Parameters3/5

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

Schema description coverage is 100% and the single slug parameter is already documented as optional with its fallback behavior, so the description adds no meaning beyond the schema. The enum-like detail about `status.kind` values describes return data, not parameter semantics. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource (the listings an account owns) and enumerates what the owner dashboard shows about each, which makes the tool distinguishable from get_listing and search_listings. The opening clause 'What the Landlord Bench owner dashboard shows about the listings an account owns' is clear but phrased as a noun clause rather than a direct verb, adding a small parsing cost.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is scoped by the 'Only for the account itself' constraint and by the note that corrections must go through the dashboard's request form, which tells the agent this is not a mutation path. However, no sibling tool is named as an alternative for the cases this tool doesn't cover (e.g. searching or comparing listings), so the agent must infer the boundary.

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

All Landlord Bench tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?