shiply

Update one of my listings

update_listing

Idempotent

Patch a listing by siteSlug — change price, pitch, terms, jurisdiction, or status (draft|live|paused). Sold listings cannot be edited. Status transitions enforced server-side. Use to pause sales or drop the price.

Input Schema

TableJSON Schema

Name	Required	Description
`pitch`	No	new sales pitch (null to clear)
`status`	No	new listing status
`siteSlug`	Yes	slug of the listed site to patch
`termsMode`	No	'standard' template or 'custom' terms
`priceCents`	No	new whole-dollar price in cents, 100–999900
`termsCustom`	No	new custom terms text (null to clear)
`jurisdiction`	No	governing jurisdiction, e.g. 'California, USA'

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedJun 23, 2026

addedInput schema / properties / jurisdiction / description

Added value: +"governing jurisdiction, e.g. 'California, USA'"

addedInput schema / properties / pitch / description
```
Added value: +"new sales pitch (null to clear)"
```

addedInput schema / properties / priceCents / description

Added value: +"new whole-dollar price in cents, 100–999900"

addedInput schema / properties / siteSlug / description
```
Added value: +"slug of the listed site to patch"
```
addedInput schema / properties / status / description
```
Added value: +"new listing status"
```
addedInput schema / properties / termsCustom / description
```
Added value: +"new custom terms text (null to clear)"
```

addedInput schema / properties / termsMode / description

Added value: +"'standard' template or 'custom' terms"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "result": {}
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}

First observedJun 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Discloses that sold listings are immutable and that status transitions are enforced server-side. Annotations only provide idempotentHint, so the description adds valuable behavioral context beyond that.

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, front-loaded with the primary action and followed by key constraints and example uses. No extraneous words.

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?

Covers the main functionality, constraints, and examples. An output schema exists to describe return values, and the description does not need to repeat that. Could mention idempotency, but annotations already cover that.

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 coverage is 100% (all parameters have descriptions). The description summarizes fields but adds no new per-parameter semantics beyond what the schema already provides, meeting the baseline.

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 explicitly states the tool patches a listing by siteSlug and lists the modifiable fields (price, pitch, terms, jurisdiction, status). This clearly distinguishes it from create_listing and delete_listing among siblings.

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 concrete use cases ('Use to pause sales or drop the price') and a constraint ('Sold listings cannot be edited'). However, it does not explicitly contrast with alternative tools like create_listing.

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

All shiply 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.

Resources

Need Help?