Seerxo

Name: Seerxo
Author: semihbugrasezer

Server Details

Generate SEO-optimized Etsy listings — title, description, and 13 tags — from your AI assistant.

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status: Unhealthy
Uptime: 11.2% over 53 days
Last Tested: 2026-10-09 20:33
Transport: Streamable HTTP · MCP 2025-11-25
URL
Repository: semihbugrasezer/seerxo
GitHub Stars: 28
Server Listing: Etsy SEO Generator

TDQS

A4/5.0

Scored 2026-10-01 00:25 across 5 tools

Disambiguation4/5

Each tool targets a fairly distinct action: generate (new listing), optimize (rewrite existing), analyze (audit), suggest keywords, and check quota. There is mild potential overlap between generate_etsy_seo and seerxo_optimize_listing since both produce listing content, but descriptions clearly separate from-scratch creation from audit-driven rewriting.

Naming Consistency3/5

Most tools follow a verb_noun pattern with a seerxo_ prefix, but generate_etsy_seo breaks both conventions—no prefix and object-first ordering (etsy_seo rather than a verb). The deviation is minor but noticeable against the otherwise consistent set.

Tool Count5/5

Five tools is well-scoped for an Etsy SEO assistant, covering the core workflow stages (keywords, generate, analyze, optimize) plus a quota check. Each tool clearly earns its place without redundancy.

Completeness4/5

The set covers a solid lifecycle: keyword discovery, listing generation, auditing, optimization, and quota tracking. Minor gaps like comparing multiple listings or managing/tracking saved listings exist, but core Etsy SEO workflows are well covered.

Available Tools

5 tools

generate_etsy_seoGenerate Etsy listingAInspect

Use this when the user wants a complete SEO-optimized Etsy listing from a product idea. Returns a title, A/B title variants, description, exactly 13 tags, and attributes. Uses one generation from the monthly quota.

ParametersJSON Schema

Name	Required	Description	Default
`category`	No	Etsy category, e.g. "Home & Living"
`product_name`	Yes	Product description, e.g. "handmade ceramic coffee mug, speckled glaze, 12oz"

Output Schema

ParametersJSON Schema

Name	Required	Description
`tags`	Yes	All 13 Etsy tags.
`title`	Yes	Primary SEO title.
`usage`	Yes
`features`	Yes	Product feature highlights.
`cross_sell`	Yes	Suggested complementary product.
`description`	Yes	SEO-optimized product description.
`shipping_tip`	Yes	Shipping pricing guidance.
`target_keywords`	Yes	Primary keyword phrases targeted by the listing.
`title_alternatives`	Yes	Alternative titles for A/B testing.
`suggested_attributes`	Yes	Suggested Etsy attribute values.

TDQS

A4/5.0

Behavior4/5

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

Annotations cover the safety profile (not read-only, not destructive, not idempotent), and the description adds genuinely new context: it consumes 'one generation from the monthly quota,' which explains the cost of repeat calls. No auth or failure behavior is described, but the quota disclosure is meaningful added value.

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 short sentences with zero waste: when-to-use is front-loaded, followed by returns and the quota cost. Every sentence earns its place.

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?

Output schema exists, so the return enumeration is a helpful bonus rather than a necessity. The quota note covers the main behavioral risk for a non-idempotent generation tool; only auth/prerequisite details are absent, which is a minor gap.

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% with only two parameters, both fully documented in the schema (category with example, product_name with length constraints). The description adds no parameter guidance beyond what the schema already provides, 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?

States a specific verb ('generate') and resource ('SEO-optimized Etsy listing') and clarifies the input is a product idea. It distinguishes itself reasonably well from analyze/optimize siblings by framing the tool as creating a listing from scratch, though it never names those siblings explicitly.

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 a complete SEO-optimized Etsy listing from a product idea" gives a clear triggering condition, and the 'complete' framing implies it is not for partial edits. No explicit exclusions or named alternatives (optimize_listing, suggest_keywords) are provided, so the agent must infer boundaries.

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

seerxo_analyze_listingAudit Etsy listingA

Read-onlyIdempotent

Inspect

Use this when the user wants to assess an existing Etsy listing. Returns a versioned Listing Readiness score with official Etsy sources, limitations, weak points, missing keywords, and tag utilization. It does not predict search rank or sales. Free — does not use quota.

ParametersJSON Schema

Name	Required	Description
`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

ParametersJSON Schema

Name	Required	Description
`fixes`	Yes	Legacy actionable fix list.
`grade`	Yes	Legacy letter grade derived from the readiness score.
`total`	Yes	Total number of SEO checks.
`checks`	Yes	All evaluated SEO checks.
`passed`	Yes	Number of SEO checks that passed.
`percent`	Yes	Legacy alias for the overall readiness score.
`coverage`	Yes	Percentage of product keywords covered by the listing.
`evidence`	Yes	Official Etsy sources used by this scoring version.
`seoScore`	Yes	Deprecated compatibility alias for overallScore.
`scoreType`	Yes
`subScores`	Yes
`weakPoints`	Yes	Ranked, sourced readiness findings and fixes.
`evaluatedAt`	Yes	ISO-8601 evaluation timestamp.
`limitations`	Yes	Important fields and outcomes this audit does not evaluate.
`overallScore`	Yes	Deterministic Listing Readiness score from 0 to 100; not a ranking prediction.
`scoringVersion`	Yes
`tagUtilization`	Yes
`missingKeywords`	Yes	Product keywords missing from the listing.

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond them: output shape (versioned score plus sources and limitations), explicit scope limits (no rank/sales prediction), and cost behavior ('Free — does not use quota'), which the annotations cannot express.

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 trigger, followed by outputs, then boundaries and cost. Every sentence earns its place and no wording is redundant.

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 an output schema present, the description need not detail return values, and it nonetheless summarizes them well; annotations cover safety and the cost note covers quota. The only gap is routing — it does not indicate which sibling to use when the user actually wants optimization rather than auditing.

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 each field (title, tags, description, product_name) is documented in the schema, so a baseline of 3 is correct. The description contributes nothing about input format, which fields drive which findings, or whether any input is required (the schema marks all optional).

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?

States a specific verb+resource ('assess an existing Etsy listing') and enumerates the concrete outputs (Listing Readiness score, weak points, missing keywords, tag utilization). It implicitly separates itself from seerxo_optimize_listing (assess vs. change), but never names a sibling explicitly.

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?

Gives a clear trigger ('when the user wants to assess an existing Etsy listing') and a valuable non-goal ('does not predict search rank or sales'). It does not, however, say when to prefer this over seerxo_optimize_listing or generate_etsy_seo for a given user intent.

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

seerxo_optimize_listingOptimize Etsy listingAInspect

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.

ParametersJSON 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

ParametersJSON 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.

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.

seerxo_quotaCheck quotaA

Read-onlyIdempotent

Inspect

Use this when the user asks about Seerxo credits or usage. Shows the authenticated account's remaining monthly generation quota. Free.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

Output Schema

ParametersJSON Schema

Name	Required	Description
`tier`	Yes	Seerxo account tier.
`limit`	Yes	Monthly generation limit.
`current`	Yes	Generations used this month.
`remaining`	Yes	Generations remaining this month.
`usageByChannel`	Yes

TDQS

A4.5/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 safety profile is covered. The description adds genuinely new context beyond the schema: the scope is limited to the authenticated account, and the call is 'Free' (no credit cost), which is material information for an agent deciding whether to invoke.

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 short sentences, zero filler, with the usage trigger front-loaded ahead of the capability statement and the cost note.

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?

An output schema exists so return values need no explanation, there are no parameters to document, and the annotations carry the safety profile. Nothing an agent needs in order to invoke this correctly is missing.

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?

The tool takes zero parameters, so per the rubric the baseline is 4; there is no parameter surface the description needs to explain.

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?

States a specific verb and resource ('Shows the authenticated account's remaining monthly generation quota'), which is immediately distinguishable from the generation/analysis siblings like generate_etsy_seo and seerxo_analyze_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?

Gives an explicit trigger ('Use this when the user asks about Seerxo credits or usage'), which is exactly the routing signal an agent needs. No alternatives are named, but no sibling competes for this intent.

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

seerxo_suggest_keywordsSuggest Etsy keywordsAInspect

Use this when the user wants Etsy keyword ideas for a product or listing. Returns ranked autosuggest phrases with relative demand and placement guidance; never fabricates search volumes. Uses one generation from the monthly quota.

ParametersJSON Schema

Name	Required	Description
`seed`	No	Seed phrase to expand
`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

ParametersJSON Schema

Name	Required	Description
`seed`	Yes	Normalized seed phrase used for suggestions.
`usage`	Yes
`source`	Yes	Source used for keyword suggestions.
`keywords`	Yes	Keyword suggestions in Etsy autosuggest demand order.
`confidence`	Yes	Confidence in the available suggestions.

TDQS

A3.8/5.0

Behavior4/5

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

Adds real context beyond the annotations: it declares the output is ranked autosuggest phrases with relative demand and placement guidance, explicitly promises not to fabricate search volumes, and warns that each call consumes one generation from the monthly quota. The quota cost explains the non-readOnly hint. It stops short of describing failure modes or what happens when quota is exhausted.

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 short sentences, front-loaded with the when-to-use condition, then output nature, then cost. Every sentence carries information and nothing is padded.

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 an output schema present, the description correctly avoids restating return values and instead covers trigger, output character, and quota cost. The one gap is that all five parameters are optional yet the tool presumably needs at least a seed, title, or product_name; the description never says which input is actually required.

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%, so the schema already documents all five parameters with constraints and an example. The description adds no syntax or format guidance beyond that, so 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?

States a specific verb and resource: producing Etsy keyword ideas for a product or listing, with a concrete output shape (ranked autosuggest phrases). It does not explicitly name or contrast itself with siblings like generate_etsy_seo or seerxo_analyze_listing, so differentiation is left partly to inference.

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?

"Use this when the user wants Etsy keyword ideas for a product or listing" gives a clear triggering condition, but there is no when-not guidance and no routing among the sibling tools that also touch Etsy listings. Usage is implied rather than bounded.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

2 tool updatesOct 1, 2026

Changedseerxo_analyze_listing23 fields changed

addedOutput schema / properties / evaluatedAt

Added value: +{
+  "description": "ISO-8601 evaluation timestamp.",
+  "type": "string"
+}

addedOutput schema / properties / evidence

Added value: +{
+  "description": "Official Etsy sources used by this scoring version.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "type": "string"
+      },
+      "source": {
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      },
+      "url": {
+        "format": "uri",
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "source",
+      "title",
+      "url"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / properties / grade / description

Previous value: -"Letter grade derived from the SEO score."New value: +"Legacy letter grade derived from the readiness score."

addedOutput schema / properties / limitations

Added value: +{
+  "description": "Important fields and outcomes this audit does not evaluate.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / missingKeywords / items / $ref
```
Added value: +"#/properties/limitations/items"
```
removedOutput schema / properties / missingKeywords / items / type
```
Removed value: -"string"
```

addedOutput schema / properties / overallScore

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

changedOutput schema / properties / percent / description

Previous value: -"Legacy alias for the overall SEO score."New value: +"Legacy alias for the overall readiness score."

addedOutput schema / properties / scoreType

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

addedOutput schema / properties / scoringVersion

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

changedOutput schema / properties / seoScore / description

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

changedOutput schema / 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 / subScores / properties / tags / description

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

changedOutput schema / 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 / tagUtilization / properties / duplicates / items / $ref

Previous value: -"#/properties/missingKeywords/items"New value: +"#/properties/limitations/items"

changedOutput schema / properties / tagUtilization / properties / overLong / items / $ref

Previous value: -"#/properties/missingKeywords/items"New value: +"#/properties/limitations/items"

changedOutput schema / properties / tagUtilization / properties / tooBroad / items / $ref

Previous value: -"#/properties/missingKeywords/items"New value: +"#/properties/limitations/items"

changedOutput schema / properties / weakPoints / description

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

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

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

addedOutput schema / properties / weakPoints / items / properties / ruleId

Added value: +{
+  "description": "Version-stable rule identifier.",
+  "type": "string"
+}

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

Added value: +{
+  "additionalProperties": false,
+  "description": "Official Etsy source connected to this finding.",
+  "properties": {
+    "id": {
+      "$ref": "#/properties/evidence/items/properties/id"
+    },
+    "source": {
+      "$ref": "#/properties/evidence/items/properties/source"
+    },
+    "title": {
+      "$ref": "#/properties/evidence/items/properties/title"
+    },
+    "url": {
+      "$ref": "#/properties/evidence/items/properties/url"
+    }
+  },
+  "required": [
+    "id",
+    "source",
+    "title",
+    "url"
+  ],
+  "type": "object"
+}

changedOutput schema / properties / weakPoints / items / required

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

changedOutput schema / required

Previous value: -[
-  "seoScore",
-  "subScores",
-  "weakPoints",
-  "missingKeywords",
-  "tagUtilization",
-  "percent",
-  "grade",
-  "coverage",
-  "passed",
-  "total",
-  "fixes",
-  "checks"
-]New value: +[
+  "scoringVersion",
+  "scoreType",
+  "overallScore",
+  "evaluatedAt",
+  "evidence",
+  "limitations",
+  "seoScore",
+  "subScores",
+  "weakPoints",
+  "missingKeywords",
+  "tagUtilization",
+  "percent",
+  "grade",
+  "coverage",
+  "passed",
+  "total",
+  "fixes",
+  "checks"
+]

Changedseerxo_optimize_listing20 fields changed

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."

5 tool updatesJul 18, 2026
- First observedgenerate_etsy_seo
- First observedseerxo_analyze_listing
- First observedseerxo_optimize_listing
- First observedseerxo_quota
- First observedseerxo_suggest_keywords

Related MCP Connectors

EverAlice Studio
io.github.Pixel-Aly
AI listing workflow for Etsy sellers: listings, images, mockups, KDP copy & ad copy. 14 tools.
E-commerce & Retail Marketing Design Tools
2
ProductifyOAuth
com.useproductify
Create, write and publish Printify products from chat, after a preview you approve.
E-commerce & Retail App Automation
1
Prelo
com.listprelo
Drafts eBay listings from your item photos: title, description, price and condition.
E-commerce & Retail Image & Video Processing
1
FanvaultOAuth
io.github.thefanvault
Run storefronts, listings, orders, content, fulfillment, and analytics through AI.
E-commerce & Retail Content Management Systems Data Visualization
2

Related MCP Servers

EverAlice AI
E-commerce & Retail Marketing AI & Machine Learning
Pixel-Aly
A
license
Not graded
quality
D
maintenance
AI listing workflow for Etsy sellers: listings, mockups, ZIP packs, KDP copy, planners, images, and ad copy.
Updated 4 months ago (2026-05-30 14:10 UTC)
MIT
Etsy MCP Server
E-commerce & Retail Search
administrativetrick
A
license
A
quality
D
maintenance
Enables AI assistants to search for products, retrieve listing details, get shop information, discover trending items, and access reviews on Etsy through the Etsy API v3.
Updated 10 months ago (2025-12-12 21:38 UTC)
7
16
MIT
ai.studio/etsy-gold
E-commerce & Retail Finance Marketing
MaximKonovalovDev
F
license
B
quality
C
maintenance
Enables Etsy sellers to manage their shops via natural language, including listing CRUD, bulk price and quantity updates by SKU, whole-shop A-F grade audits, photo uploads, shipping profiles, conversations, receipts, fulfillment tracking, and profit calculation.
Updated a month ago (2026-08-29 21:00 UTC)
19
-
Etsy MCP Server
E-commerce & Retail Search
pipeworx-io
A
license
Not graded
quality
B
maintenance
Enables AI agents to search active Etsy listings site-wide or within a specific shop, and to fetch individual listing details by ID, using an Etsy API key. Queries support keyword, price, taxonomy, and sort filters, returning live active-listing data only.
Updated 8 days ago (2026-10-02 22:53 UTC)
86 npm
MIT

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.

Server Details

Available Tools

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Tool Schema Changelog

Related MCP Connectors

Related MCP Servers

Glama MCP Gateway

Resources