Skip to main content
Glama

list_my_items

Retrieve and display the items you can manage from your current account's profile, with an optional limit to control how many listings are returned.

Instructions

列出当前账号在个人主页可管理的商品

Args: limit: 数量限制

Returns: 商品列表

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_my_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose two useful behavioral facts: the operation is scoped to the authenticated account ('当前账号') and returns only items that are manageable from the personal homepage, not all items. It says nothing about ordering, pagination behavior beyond the limit, or whether results include unpublished/draft items.

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

Conciseness3/5

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

The purpose sentence is front-loaded and clear, and the Args/Returns block aids scanning, but both blocks largely restate the schema (limit) or a single obvious fact (returns an item list). Short overall with little wasted prose, but also very little content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with no output schema, the description covers what it lists and roughly what comes back, which is close to sufficient. Gaps remain around pagination/limit semantics and result ordering, which matter because callers will page through this listing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description only restates the parameter name as '数量限制' (quantity limit). It omits the default of 20, any maximum, and what happens when the parameter is omitted, so it adds essentially no meaning beyond the schema property name.

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 ('列出' / list) and resource ('商品' / items) plus a meaningful scope: items the current account can manage on its personal homepage. That scope distinguishes it from a generic search, though it never names the sibling tools (search_items, get_top_items) it differs from.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. An agent must infer from '可管理的商品' that this is the self-scoped listing rather than a search across all items, which is weak routing information given siblings like search_items and get_top_items exist.

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