kinsta_analytics_top-client-ipsIdentify the client IP addresses generating the most traffic on a Kinsta site. Use environment ID and optional date filters to retrieve analytics for custom or predefined periods.
Get top client IP addresses.
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | Custom end date (YYYY-MM-DD) | |
| from | No | Custom start date (YYYY-MM-DD) | |
| env_id | Yes | The environment ID | |
| time_span | No |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. However, the description adds no behavioral context beyond the simple read operation, such as whether results are sorted, limited, or affected by date parameters. No contradiction exists.
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 sentence with no filler or repetition. It states the operation and object directly, making it immediately scannable and appropriately sized for a simple analytics read tool.
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?
For a simple read-only tool with a small schema, the description is minimally adequate. However, there is no output schema, and the description does not clarify ranking semantics, default time windows, or response shape. These are not fatal gaps, but they leave the agent without enough context for a fully informed invocation.
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 75%, with to, from, and env_id having descriptions and time_span having a self-explanatory enum. The description adds no parameter-level detail, but the schema mostly carries the burden. The uncovered time_span parameter is still understandable from its enum values, so the lack of description-level compensation is acceptable.
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 clear verb and resource: 'Get top client IP addresses.' It states exactly what the tool returns and is sufficiently distinct from sibling analytics tools such as top-countries or top-referrers by naming a specific resource. It does not explicitly contrast itself with any sibling, but the resource alone makes the purpose unambiguous.
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?
There is no guidance about when to use this tool versus the many other analytics top-* endpoints or the broader analytics family. The description does not mention conditions, alternatives, or exclusions, so agents must infer usage solely from the name and schema.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.