Send harvest requests to all connected marketplaces to synchronize product data and orders.
Send harvest request to all your marketplaces
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": "HarvestAllV3"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| storeId | No | The StoreId to filter by |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, and the description fails to disclose side effects, destructiveness, idempotency, auth requirements, or rate limits. 'Send harvest request' implies a mutation but offers no detail on what happens to data or system state.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that directly states the action. However, it is slightly too sparse given the lack of annotations and missing context; a couple more sentences would be warranted.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Without an output schema, the description should explain what the user can expect from the harvest request (e.g., a response, a job ID, or a side effect on data). It does not cover return values, async behavior, or error conditions, leaving the tool incomplete for an agent to use correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The only parameter ('storeId') already has a clear schema description ('The StoreId to filter by') with 100% coverage. The tool description adds no additional meaning or constraints beyond what the schema provides, thus meeting the baseline without extra value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Send harvest request') and identifies the resource ('all your marketplaces'), but the term 'harvest' is domain jargon and the exact action (what sending a request entails) is unclear. It distinguishes from sibling tools only by version number (V3), not by functional difference.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives like HarvestAll (non-V3), HarvestAccount, HarvestOrder, or HarvestOrderV3. The description does not mention prerequisites, conditions, or expected outcomes.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.