Skip to main content
Glama
Sign In

Sellfy MCP Server

by com.sellfy
OverviewDiscussionsAdmin

List store versions

list_store_versions
Read-only

List store versions, newest first, with their preview_url. kind="draft" is an editable draft; kind="backup" is a read-only copy of the live store taken automatically just before a publish or restore replaced it (the two newest are kept) - restore_store_version brings one back. Edits made in the Sellfy dashboard are not versioned.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_store_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
versionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint, so the safety profile is covered; the description adds genuinely new behavior: result ordering, backup retention (only the two newest are kept), and the fact that dashboard edits are unversioned. It doesn't mention pagination or limits on how many versions are returned, which is the remaining gap.

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

Conciseness4/5

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

Two dense sentences, front-loaded with the verb and ordering, with the retention and caveat details following. The parenthetical retention clause makes the second sentence heavy, but nothing is filler.

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?

Zero-parameter, read-only list tool with an output schema, so return values needn't be spelled out. Ordering, kind semantics, retention policy, the dashboard caveat, and the recovery path via restore_store_version together cover everything an agent needs before calling.

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 no parameters, so the baseline is 4. The description's discussion of kind="draft" vs kind="backup" adds useful meaning about the returned data even though it isn't an input.

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 ("List store versions"), adds the ordering guarantee ("newest first") and a returned field ("preview_url"). It also distinguishes the two version kinds, so an agent knows what it will get without opening the schema.

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?

Explains the semantics of each kind and routes the agent to restore_store_version for recovery, plus warns that dashboard edits are not versioned. It stops short of an explicit "use this instead of X" statement, but with no near-duplicate list sibling that is a minor gap.

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

All Sellfy MCP Server 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