Get recent click data for the workspace
| Name | Required | Description | Default |
|---|---|---|---|
| link_id | No | Optional: filter clicks by link ID |
| Name | Required | Description | Default |
|---|---|---|---|
| results | No |
Changes observed during successful MCP inspections.
Output schema / requiredRemoved value: -[
- "results"
-]Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": true,
+ "description": "Time-series click data",
+ "properties": {
+ "results": {
+ "type": "array"
+ }
+ },
+ "required": [
+ "results"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety profile is clear. Description adds 'recent' but does not specify time range, pagination, or other key behaviors. With strong annotations, a score of 3 is appropriate.
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?
Single sentence is concise and front-loaded. However, the description could be more informative without losing conciseness, e.g., specifying what 'recent' means.
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?
Tool is simple with one optional param and output schema exists. However, missing details like the typical time window for 'recent' and whether results are paginated. Adequate but not comprehensive.
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 coverage is 100% for the single parameter 'link_id', which already has a description. The tool description adds no further meaning beyond what the schema provides.
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?
Description uses specific verb+resource ('Get recent click data') and scope ('workspace'). It is clear but does not differentiate from siblings like 'export_clicks' or 'get_analytics' which may also involve click data.
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 on when to use this tool vs alternatives such as 'export_clicks' or 'get_analytics_by'. No context on prerequisites or limitations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.