Skip to main content
Glama

sellfox_custom_report

sellfox_custom_report

Fetch custom report data from Sellfox. Define your report in the web interface, then use its report ID to retrieve filtered, sorted, and dimensioned sales, advertising, and inventory metrics.

Instructions

获取自定义报表列表数据。需先在 Web 界面创建报表,获取 reportId 后使用。支持丰富的筛选、排序和商品维度参数。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
devIdsNo业务员筛选,多个使用逗号分隔
endDateYes统计结束时间 yyyy-MM-dd
shopIdsNo店铺筛选,多个使用逗号分隔
brandIdsNo品牌筛选,多个使用逗号分隔
currencyNo币种(为空时使用原币种)
fullCidsNo分类筛选,多个使用逗号分隔
labelIdsNo标签筛选,多个使用逗号分隔
reportIdYes报表ID,在Web界面报表中可找到此ID
sortTypeNo排序类型: asc=升序, desc=降序
sortIndexNo排序指标,可选报表中任意字段名。常用: salePrice(销售额), saleNum(销量), orderNum(订单量), profitPrice(毛利润), profitRate(毛利率), adCost(广告花费), acos(ACoS), roas(ROAS), sessions(Sessions), conversionRate(转化率), fbaInventory(FBA可用), refundRate(退款率)
startDateYes统计开始时间 yyyy-MM-dd
productDimNo商品维度(商品维度的报表需要传递此参数)
searchModeNo搜索模式: exact=精确, blur=模糊
searchTypeNo搜索类型
openEndDateNo上架结束日期 yyyy-MM-dd
operatorIdsNo开发员筛选,多个使用逗号分隔
onlineStatusNo产品状态筛选,多个使用逗号分隔
openStartDateNo上架开始日期 yyyy-MM-dd
searchContentNo搜索内容
marketplaceIdsNo站点筛选,多个使用逗号分隔
Behavior2/5

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

No annotations are provided. The description hints at a read operation with filtering and sorting but does not disclose side effects, authorization needs, rate limits, or error handling behavior.

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 succinct sentences: purpose, prerequisite, and feature summary. No redundancy.

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 20 parameters, no output schema, and no annotations, the description lacks details on return format, pagination, error cases, and behavior with missing data, making it insufficient for complex usage.

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 coverage is 100%, so the baseline is 3. The description adds prerequisite context (need report ID) but does not elaborate on individual parameters beyond the schema.

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 clearly states the tool retrieves custom report list data and requires a pre-created report. However, it does not explicitly differentiate from sibling report tools, though the name is specific.

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 mentions the prerequisite of creating a report in the web interface, but lacks guidance on when to use this tool versus alternatives or when to avoid it.

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