Skip to main content
Glama
stan13

ripper-mcp

by stan13

update_listing

Update a listing's details and pipeline status (e.g., set as pending or sold with sale date/price). Only modify fields you specify; requires listingId from find_listings.

Instructions

Update a listing — including moving it through the pipeline (e.g. set status to pending or sold, with saleDate/salePrice). Only include the fields you want to change. Use find_listings first to get the listingId.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNo
notesNoInternal agent notes about the listing.
stateNo
statusNoPipeline stage of the listing.
addressNoStreet address of the property.
lotSizeNoLot size in sq ft or acres.
zipCodeNo
bedroomsNo
listDateNoISO 8601 date the listing went live.
saleDateNoISO 8601 date it sold.
bathroomsNo
contactIdNoReassign the listing to this owning contact.
listPriceNoAsking price in dollars.
listingIdYesId of the listing to update (from find_listings).
mlsNumberNo
salePriceNoFinal sale price in dollars.
yearBuiltNo
squareFeetNo
descriptionNoPublic-facing property description.
propertyTypeNo
expirationDateNoISO 8601 date the listing agreement expires.
Behavior3/5

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

No annotations provided, so description carries full burden. It implies partial updates ('Only include the fields you want to change') but lacks details on side effects, permissions, or idempotency.

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

Conciseness5/5

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

Two sentences, no fluff, front-loaded with purpose and example.

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

Completeness2/5

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

For a tool with 21 parameters and no output schema, the description is too minimal. Missing details on return values, error handling, and exact semantics of status transitions.

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 57%. The description adds limited value beyond schema, mainly emphasizing pipeline status and partial updates. Many parameters have schema descriptions already.

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 clearly states the verb 'Update' and resource 'listing', with a pipeline example. However, it does not explicitly differentiate from sibling tools like create_listing.

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 guidance to only include changed fields and use find_listings first. No mention of when not to use this tool or alternatives like create_listing.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/stan13/ripper-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server