Retrieve a specific number of the most recent tracked clicks from your store.
Get the latest tracked clicks
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": "GetStoreTrackedClicks"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| count | No | The amount of clicks to retrieve |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden but only states 'Get the latest tracked clicks'. It does not disclose read-only nature, authentication requirements, rate limits, or behavior when count is omitted. Significant gaps for a mutation-unaware agent.
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 short sentence, which is concise but lacks structure and depth. It could include usage context or example without losing brevity.
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?
Given no output schema and no annotations, the description is insufficient for a tool with many siblings. It omits output format, definition of 'tracked clicks', and behavior details. The 'latest' qualifier adds minimal value.
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?
Schema covers 100% of the single parameter 'count' with description 'The amount of clicks to retrieve'. The tool description adds 'latest' but no further semantics (e.g., default, max, effect of omission), meeting baseline but not exceeding it.
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 clearly states the verb 'Get' and the resource 'latest tracked clicks', making the tool's purpose understandable. However, it does not distinguish from similar sibling tools like GetStoreTrackedOrders or GetStoreTrackedExternalOrders, missing an opportunity to clarify scope.
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 such as GetStoreTrackedOrders or GetTrackingStatus. The description lacks context for selecting this tool among many similar 'GetStore...' tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.