Seerxo

Optimize Etsy listing

seerxo_optimize_listing

Use this when the user wants to rewrite an existing Etsy title, description, or tags based on audit findings. A re-audit gate prevents score regression. Uses one generation from the monthly quota.

Input Schema

TableJSON Schema

Name	Required	Description
`mode`	No	Which fields to rewrite (default: full)
`tags`	No	Current Etsy tags
`title`	No	Current Etsy listing title
`description`	No	Current Etsy listing description
`product_name`	No	Short product description, e.g. "handmade ceramic coffee mug, speckled glaze, 12oz"

Output Schema

TableJSON Schema

Name	Required	Description
`diff`	Yes	Before and after values for each listing field.
`mode`	Yes	Optimization mode that was applied.
`after`	Yes	Audit summary after optimization.
`usage`	Yes
`before`	Yes	Audit summary before optimization.
`fallback`	Yes	Whether the original listing was kept to prevent a score regression.
`resolved`	Yes	Finding IDs resolved by the rewrite.
`optimized`	Yes
`unresolved`	Yes	Finding IDs still present after the rewrite.

Schema Changelog

Changes observed during successful MCP inspections.

Changed20 schema fields changedOct 1, 2026

addedOutput schema / properties / after / properties / overallScore

Added value: +{
+  "$ref": "#/properties/before/properties/overallScore"
+}

addedOutput schema / properties / after / properties / scoreType

Added value: +{
+  "$ref": "#/properties/before/properties/scoreType"
+}

addedOutput schema / properties / after / properties / scoringVersion

Added value: +{
+  "$ref": "#/properties/before/properties/scoringVersion"
+}

changedOutput schema / properties / after / required

Previous value: -[
-  "seoScore",
-  "subScores",
-  "weakPoints"
-]New value: +[
+  "scoringVersion",
+  "scoreType",
+  "overallScore",
+  "seoScore",
+  "subScores",
+  "weakPoints"
+]

addedOutput schema / properties / before / properties / overallScore

Added value: +{
+  "description": "Deterministic Listing Readiness score from 0 to 100.",
+  "type": "number"
+}

addedOutput schema / properties / before / properties / scoreType

Added value: +{
+  "const": "listing_readiness",
+  "type": "string"
+}

addedOutput schema / properties / before / properties / scoringVersion

Added value: +{
+  "const": "etsy-guidance-2026-04-27",
+  "type": "string"
+}

changedOutput schema / properties / before / properties / seoScore / description

Previous value: -"Overall Etsy SEO score from 0 to 100."New value: +"Deprecated compatibility alias for overallScore."

changedOutput schema / properties / before / properties / subScores / properties / description / description

Previous value: -"Description SEO score from 0 to 100."New value: +"Description readiness from 0 to 100."

changedOutput schema / properties / before / properties / subScores / properties / tags / description
```
Previous value: -"Tags SEO score from 0 to 100."New value: +"Tag readiness from 0 to 100."
```
changedOutput schema / properties / before / properties / subScores / properties / title / description
```
Previous value: -"Title SEO score from 0 to 100."New value: +"Title readiness from 0 to 100."
```

changedOutput schema / properties / before / properties / weakPoints / description

Previous value: -"Ranked SEO findings and fixes."New value: +"Ranked, sourced readiness findings and fixes."

addedOutput schema / properties / before / properties / weakPoints / items / properties / explanation

Added value: +{
+  "description": "Why the deterministic rule produced this finding.",
+  "type": "string"
+}

addedOutput schema / properties / before / properties / weakPoints / items / properties / ruleId
```
Added value: +{
+  "description": "Version-stable rule identifier.",
+  "type": "string"
+}
```

addedOutput schema / properties / before / properties / weakPoints / items / properties / source

Added value: +{
+  "additionalProperties": false,
+  "description": "Official Etsy source connected to this finding.",
+  "properties": {
+    "id": {
+      "type": "string"
+    },
+    "source": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "url": {
+      "format": "uri",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "source",
+    "title",
+    "url"
+  ],
+  "type": "object"
+}

changedOutput schema / properties / before / properties / weakPoints / items / required

Previous value: -[
-  "id",
-  "field",
-  "severity",
-  "reason",
-  "fix"
-]New value: +[
+  "id",
+  "ruleId",
+  "field",
+  "severity",
+  "reason",
+  "explanation",
+  "fix",
+  "source"
+]

changedOutput schema / properties / before / required

Previous value: -[
-  "seoScore",
-  "subScores",
-  "weakPoints"
-]New value: +[
+  "scoringVersion",
+  "scoreType",
+  "overallScore",
+  "seoScore",
+  "subScores",
+  "weakPoints"
+]

changedOutput schema / properties / optimized / properties / description / description

Previous value: -"SEO-optimized Etsy listing description."New value: +"Etsy listing description."

changedOutput schema / properties / optimized / properties / tags / description

Previous value: -"SEO-optimized Etsy tags."New value: +"Etsy listing tags."

changedOutput schema / properties / optimized / properties / title / description

Previous value: -"SEO-optimized Etsy listing title."New value: +"Etsy listing title."

First observedJul 18, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations declare the safety profile (readOnlyHint=false, destructiveHint=false), so the description only needs to add context. It does: the re-audit gate that prevents score regression and the fact that one monthly-quota generation is consumed. These are non-obvious behavioral facts an agent cannot derive from structured fields. It does not state what happens to the prior title/description, but the annotations plus this content cover the essentials.

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?

Three sentences, front-loaded with the usage condition, and every sentence earns its place: purpose, quality gate, and quota cost. No filler.

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?

An output schema exists, so return values need not be explained, and annotations carry the safety profile. The description adds the quota and re-audit gate, leaving little an agent needs missing. It could note prerequisites (an existing audit) more explicitly, but it is close to 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%, so the schema already documents all five parameters including the mode enum and length bounds. The description adds no parameter-level detail, so the baseline 3 applies.

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 verb and resource: 'rewrite an existing Etsy title, description, or tags based on audit findings.' The word 'rewrite' plus 'based on audit findings' distinguishes it from the sibling generate_etsy_seo (new generation) and seerxo_analyze_listing (analysis). It does not name a sibling explicitly, so differentiation is implied rather than stated.

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?

'Use this when the user wants to rewrite an existing Etsy title, description, or tags' is a clear triggering condition, and 'based on audit findings' positions it after the audit step. There is no explicit when-not guidance or named alternative, but the usage context is unambiguous.

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

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