Skip to main content
Glama

sellfox_product_analysis

sellfox_product_analysis

Analyze Amazon product performance with browsing, sessions, ad, and sales metrics. Filter by time, category, ASIN, tags, and more to compare periods.

Instructions

获取产品分析数据(新),含浏览、会话、广告和销量指标。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descNo是否降序: true/false
tagIdNo规则ID
endDateNo结束时间 yyyy-MM-dd
fullCidNo商品分类全路径
orderByNo排序字段,默认按销量降序
asinTypeNo数据聚合维度: 1=asin, 2=parentAsin, 3=msku, 4=sku, 5=spu
currencyNo币种
devIdListNo业务员ID列表
mergeAsinNo按ASIN汇总: true/false
startDateNo开始时间 yyyy-MM-dd
adTypeListNo广告类型: sp, sd, sb, sbv, sbs
labelQueryNo产品标签查询类型: 0=任一, 1=所有
preEndDateNo自定义周期结束时间, compareType=3时生效 yyyy-MM-dd
searchModeNo搜索模式: exact=精确, blur=模糊
searchTypeNo搜索类型
shopIdListNo店铺ID列表
brandIdListNo品牌ID列表
compareTypeNo对比类型: 0=不做对比, 1=显示环比, 2=显示同比, 3=自定义周期
labelIdListNo产品标签ID列表
openDateEndNo产品创建(上架)结束时间 yyyy-MM-dd
lowCostStoreNo是否筛选低价商城
preStartDateNo自定义周期开始时间, compareType=3时生效 yyyy-MM-dd
openDateStartNo产品创建(上架)开始时间 yyyy-MM-dd
operatorIdListNo开发员ID列表
searchContentsNo搜索内容列表
onlineStatusListNo产品状态: active=可售, inActive=不可售, delete=已删除
marketplaceIdListNo站点ID列表
isNewOrMovingOrInStockNo统计范围: 0=全部有数据, 1=有库存, 2=近1年有销量, 3=近180天上架, 4=有库存或近1年有销量或近180新上架, 5=全部商品
Behavior2/5

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

No annotations provided, so description should disclose behavioral traits. Only lists included metrics; does not mention whether it is read-only, has side effects, rate limits, or pagination behavior.

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?

Single sentence is concise and front-loaded, but too minimal for a complex tool with 28 parameters. Could benefit from additional structure or context.

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

Completeness2/5

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

Given 28 parameters, no output schema, and no annotations, the description lacks necessary context. Does not explain scope (e.g., filtering by shop, marketplace) or how the data is grouped.

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 covers all 28 parameters with descriptions (100% coverage), so baseline is 3. Description adds no additional meaning beyond what schema already provides.

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?

Description clearly states it retrieves product analysis data with browsing, sessions, ads, and sales metrics. However, it does not differentiate from sibling tool sellfox_product_analysis_v2, which appears to be a newer version.

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?

No guidance on when to use this tool versus alternatives. Does not mention prerequisites or scenarios where other tools (e.g., sellfox_product_sales) would be more appropriate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shuolol/sellfox-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server