Check current SERP position and compare against previous check — tracks changes over time
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": "serp_alert"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| domain | No | Domain to watch | |
| country | No | Country code | |
| keyword | No | Keyword to monitor |
Changes observed during successful MCP inspections.
Input schema / additionalPropertiesAdded value: +falseDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose behavior and it does explain the core behavior (current position + comparison). Yet it is ambiguous whether the tool stores previous checks, requires them to exist, or has side effects. The description does not clarify data persistence or error behavior, so transparency is moderate.
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, well-structured sentence that communicates the tool's purpose and the tracking behavior without any redundancy. Every word earns its place, making it highly efficient.
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 three-parameter tool with no output schema, the description covers the primary functionality and the comparison aspect adequately. It leaves out details about return format or what happens if no previous check exists, but given the tool's simplicity, the description is reasonably complete.
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 description coverage is 100%, so each parameter (domain, keyword, country) already has a basic description. The tool description adds no further meaning beyond the schema's parameter names and brief descriptions, so it meets the baseline but does not exceed 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 tool checks current SERP position and compares against a previous check, indicating temporal change tracking. This specific verb+resource+scope differentiates it from siblings like serp_snapshot (which likely only takes a snapshot) and rank_tracker (which may track rankings over time but this tool emphasizes comparison with a stored previous check).
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?
The phrase 'tracks changes over time' provides clear context for when to use this tool: when a historical comparison of SERP position is needed. However, it does not explicitly name alternative tools or state when not to use it, so it stops short of full usage guidance.
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.