account_statusFree and instant: remaining monthly budget, credit balance, when the budget resets, and which endpoints stay free. Check this before a paid call if you are unsure the budget covers it.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, but the description fully covers behavioral traits: it is free, instant, read-only, and discloses exactly what information is provided.
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?
Two sentences, no unnecessary words, key information front-loaded. Every sentence is essential.
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?
Despite no output schema, the description fully explains what the tool returns, making the tool complete and self-contained.
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?
No parameters required; the description adds rich meaning beyond the empty schema by listing the returned data fields (budget, credit, reset time, free endpoints).
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 it provides account status info (remaining budget, credit balance, reset time, free endpoints). It distinguishes itself from sibling tools like backlink_profile by focusing on account-level financial 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?
Explicitly advises using this tool before a paid call if unsure about budget coverage, establishing a clear when-to-use directive.
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.
Each tool targets a distinct aspect of SEO analysis: budget, backlinks, competitor gaps, indexing, keyword data, page performance, query insights, and SERP positions. No two tools overlap in purpose.
All tool names follow a consistent snake_case noun_noun pattern (e.g., account_status, backlink_profile), making them predictable and easy to interpret.
With 8 tools, the server is well-scoped for SEO analysis, covering key areas without being overwhelming or too sparse.
The tool set covers major SEO analysis domains (indexing, keywords, backlinks, competitors, on-page performance), but lacks a tool for tracking changes over time or providing actionable recommendations (e.g., fix suggestions).