get_seo_trafficGet DataHouse SEO traffic aggregate data by domain, including traffic metrics, top keywords, and whois fields. (Each request consumes 1 credit.)
| Name | Required | Description | Default |
|---|---|---|---|
| domain | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses 'Each request consumes 1 credit,' which is a useful behavioral trait given the absence of annotations. However, it does not cover rate limits, authentication, or aggregation details, leaving gaps. It adds some transparency beyond the bare minimum.
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 exactly two sentences, front-loaded with the core purpose and followed by a cost note. Every word earns its place with no redundancy.
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 one-parameter tool, the description provides basic output hints (traffic metrics, keywords, whois) and the credit cost. However, it lacks parameter format details, error behavior, and assumes knowledge of what 'aggregate' means. Adequate for basic use but not fully 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?
The schema provides no description for the 'domain' parameter (0% coverage). The description only repeats the parameter name ('by domain') without explaining format, examples, or constraints. It fails to compensate for the missing schema documentation.
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', the resource 'DataHouse SEO traffic aggregate data', and the scope 'by domain'. It lists specific data types (traffic metrics, top keywords, whois fields), distinguishing it from sibling tools like get_keyword_volume or get_backlink_opportunities.
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 explicit guidance on when to use this tool vs alternatives, but the purpose is clear enough to imply usage when SEO traffic data is needed. The description does not mention exclusions or alternative tools, providing only implied context.
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.
Several tools have similar names (e.g., get_citation_domains vs get_prompt_citation_domains, and multiple opportunity tools), though the descriptions do clarify their focus. The batch prompt operations are distinct, but the abundance of getters could cause misselection.
Tools uniformly use snake_case with verb prefixes (batch_get, batch_create, get), following a clear pattern. Minor deviations like get_prompt_citation_domains vs get_citation_domains create slight inconsistency but the overall style is predictable.
With 18 tools, the server is slightly heavy per the typical 3-15 range, but not excessive. The tools cover both prompt CRUD and SEO analytics, so the count is defensible but feels crowded.
The prompt lifecycle is well covered with batch CRUD operations. The analytics side offers many read-only queries (traffic, keywords, citations, opportunities), though there are no write operations for those domains, which is acceptable for an analytical tool.