Skip to main content
Glama
Unilytics MCP Server

Unilytics MCP Server

Official

aeo_prompt_volume

Read-only

Estimates AI search volume for a given prompt, returning a volume figure and bucket to help prioritize prompt targets.

Instructions

AI search-volume estimate for a prompt (expensive multi-API pipeline). Returns {volume, bucket}.

[Provider: DataForSEO]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prompt": "<prompt>"
    },
    "name": "aeo_prompt_volume"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNo
promptYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.0
    • removedInput schema / properties / config
      Removed value: -{
      -  "default": null,
      -  "title": "config",
      -  "type": "string"
      -}
  2. First observedv1.0.0

TDQS

B3.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds genuinely new context beyond them: the call is expensive (multi-API pipeline) and it returns {volume, bucket}, which is important since no output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences plus a provider tag, front-loaded with the core purpose and the cost warning. No filler, though the provider tag is marginal value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Because there is no output schema, the inline return shape {volume, bucket} is a real contribution. However, the unexplained 'topic' parameter and the absence of any note on units, ranges, or failure behavior leave the definition only partially complete for a costly external-API call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and there are two parameters. The description only implies what 'prompt' means and says nothing about 'topic' (default empty string) or how the two interact, so it fails to compensate for the undocumented schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'AI search-volume estimate for a prompt'. An agent can tell this is a volume-lookup tool rather than a clustering or audit tool, though it never names a sibling to contrast with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The parenthetical '(expensive multi-API pipeline)' implies the tool should be used sparingly, which is useful cost guidance, but there is no explicit when-to-use/when-not-to-use statement or named alternative for cheaper volume lookups.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools