Skip to main content
Glama
Sign In
FishClaw MCP

FishClaw MCP

by TnoobT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_selling_items

Read-only

Retrieve all currently selling items from your Xianyu account, including titles, prices, and links. Automatically navigates and scrolls to load the full list.

Instructions

获取当前账号所有在售商品列表（标题、价格、链接）。 内部自动跳转个人中心并滚动加载全部商品，无需手动导航。

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": "get_selling_items"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

The description goes beyond readOnlyHint by disclosing that the tool automatically navigates to the personal center and scrolls to load all items, which is valuable behavioral context. It does not contradict annotations and provides actionable information about side effects like automated scrolling.

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?

The description is extremely concise: two sentences, front-loaded with the core purpose followed by a behavioral note. Every sentence adds value with no redundancy.

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?

For a tool with no parameters and a simple read operation, the description is fully complete. It specifies the output fields (title, price, link), indicates it's for the current account, and explains the automatic behavior. The presence of an output schema (not shown) further reduces the need for description details.

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 input schema has zero parameters, so the description does not need to add parameter information. Baseline score of 4 is appropriate as there is nothing more to clarify about parameters.

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 clearly states the tool retrieves the list of all currently selling items for the current account, including title, price, and link. It distinguishes itself from sibling tools like 'search_market' or 'manage_item' by focusing on the 'selling items' list.

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?

The description implies when to use (to get selling items) but does not explicitly contrast with alternatives like 'search_market' or give when-not-to-use guidance. It mentions automatic navigation as a convenience, which hints at its purpose but lacks explicit usage boundaries.

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

Deploy Server

Other Tools