Skip to main content
Glama

Seerxo

by io.github.semihbugrasezer
OverviewDiscussionsAdmin

Audit Etsy listing

seerxo_analyze_listing
Read-onlyIdempotent

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoCurrent Etsy tags
titleNoCurrent Etsy listing title
descriptionNoCurrent Etsy listing description
product_nameNoShort product description, e.g. "handmade ceramic coffee mug, speckled glaze, 12oz"

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
fixesYesLegacy actionable fix list.
gradeYesLegacy letter grade derived from the readiness score.
totalYesTotal number of SEO checks.
checksYesAll evaluated SEO checks.
passedYesNumber of SEO checks that passed.
percentYesLegacy alias for the overall readiness score.
coverageYesPercentage of product keywords covered by the listing.
evidenceYesOfficial Etsy sources used by this scoring version.
seoScoreYesDeprecated compatibility alias for overallScore.
scoreTypeYes
subScoresYes
weakPointsYesRanked, sourced readiness findings and fixes.
evaluatedAtYesISO-8601 evaluation timestamp.
limitationsYesImportant fields and outcomes this audit does not evaluate.
overallScoreYesDeterministic Listing Readiness score from 0 to 100; not a ranking prediction.
scoringVersionYes
tagUtilizationYes
missingKeywordsYesProduct keywords missing from the listing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed23 schema 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"
+]
  2. First observed

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.

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