Skip to main content
Glama
mingkingss230-hash

PDD-MMS-MCP

by mingkingss230-hash
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

拉取店铺评价

pdd_reviews_list

Fetch Pinduoduo merchant review lists across pages using the saved request template. Filter by pending-report status or keywords, and optionally export to CSV.

Instructions

跨页拉取 mms 后台评价列表（自动复用页面自身请求体模板）。可只看待举报、关键词过滤、导出 CSV。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
shopNo店铺名（多店铺时指定，对应 config/shops.json 的键名；省略=默认店铺）
pagesNo拉取页数
outCsvNo同时导出 CSV 到 output/
keywordNo按商品名/商品ID/评价内容过滤（本地过滤）
pageSizeNo每页条数
reportableOnlyNo只看待举报(reportState=99)的评价
refreshTemplateNo强制重新抓取页面请求体模板（接口报错/改过筛选条件时用）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

【无 annotation，描述承担全部行为披露责任】“跨页拉取”和“自动复用页面自身请求体模板”披露了分页和模板复用行为，并暗示“拉取”为读取操作。但未明确说明认证要求、失败时的行为、或导出 CSV 对文件系统的副作用（虽有参数说明，但描述未补充默认行为）。整体有一定披露，但不够完整。

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?

描述只有一句中文，核心动作“拉取评价列表”位于句首，随后用简短短语列出关键选项，没有冗余内容或与标题重复的赘述。每个词都贡献了信息，结构紧凑且前载。

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?

在无 annotation、无输出模式的情况下，描述覆盖了主要用途和关键能力，且参数模式已补充了 refreshTemplate 等细节，基本可用。但未说明返回结果的形式（是否为列表、字段结构）、依赖登录态的提醒，以及模板复用失败的常见后果，整体上下文仍留有缺口。

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?

输入模式对 7 个参数全部有详细描述，覆盖率 100%，因此基线为 3。描述中的“待举报、关键词过滤、导出 CSV”虽然映射到 reportableOnly、keyword、outCsv，但未超出模式已有的说明，也未对参数格式或边界条件增添新信息。

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?

描述给出了明确动词“拉取”和资源“mms 后台评价列表”，直接点明工具作用，且与 sibling 中的商品、推广、聊天类工具明显区分。同时列出“待举报、关键词过滤、导出 CSV”等能力，进一步明确了功能边界，代理无需查看其他工具模式即可判断用途。

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?

描述未提供任何“何时使用”或“何时不用”的指导，也没有提及替代工具或切换条件。虽然功能列表暗示了过滤和导出场景，但没有说明在什么情况下应选此工具而非其他 sibling，代理只能依赖默认推断。

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