Skip to main content
Glama

Visibility Genies

Get traffic history

get_traffic_history

Estimated organic and paid search traffic of up to 10 domains, month by month over the last 12 months, in one market. Estimated price: ~$0.25 for 2 domains, ~$0.27 for 10: one request, billed by the domains asked for. The same domains and market saved within a day are read free, and it opens free on Compare Domains. Each call may spend up to the workspace's agent spend limit ($2.00 unless changed in Settings) without asking: it holds at most its estimate plus a margin while it runs and is charged what it bought, never more. A call whose maximum is above the limit is refused before anything is bought, with its estimate and maximum: ask the user, then call again with approvedMaxCostUsd set to the amount they approved.

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": {
      "projectId": "<projectId>",
      "domains": "<domains>"
    },
    "name": "get_traffic_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYes1 to 10 domains, e.g. ['example.com', 'example.org'].
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
languageCodeNoLanguage code such as en, es or vi. When left out, the language of the project's default market is used (see list_projects).
locationCodeNoMarket location code, for example 2840 for the United States. When left out, the project's default market is used (shown by list_projects and changed in project settings). A few countries, Iceland (2352) among them, only have Google Ads data: search volume, CPC and trends are available there, but keyword difficulty, search intent and domain analytics are not.
approvedMaxCostUsdNoThe most, in USD, the user approved for this call after seeing its estimate and maximum. Only needed after a call was refused for costing more than the workspace's agent spend limit; never set it without asking the user.

Output Schema

NameRequiredDescriptionDefault
costNo
metaNo
boughtNo
savedResultIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false), the description discloses pricing scaled by domain count, a free re-read window, the workspace spend cap, the hold-and-charge-once model, and the exact refusal-and-retry behavior with approvedMaxCostUsd. This is unusually complete disclosure for a billable, open-world call.

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?

The core scope is front-loaded in the first clause, with cost and approval mechanics following in a logical order. The cost paragraph is dense but nearly every clause carries decision-relevant information; it is longer than ideal but not padded.

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

Completeness5/5

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

With a full schema, an output schema, and annotations in place, the description supplies exactly the missing layer: cost, caching, spend limits, and the approval loop. An agent has everything needed to call it and to recover from a refusal.

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

Parameters4/5

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

Schema coverage is 100%, so the parameters are already documented; the description adds the pricing logic tied to the domains array and explains the real-world workflow around approvedMaxCostUsd that the schema only states as a rule. Language and market defaulting are left entirely to the schema, which is acceptable given full coverage.

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?

The description gives a precise verb-and-resource statement: estimated organic and paid traffic for up to 10 domains, month by month, over 12 months, in a single market. That scope is specific enough to separate it from keyword, rank, or SERP history siblings, though it never names an alternative tool explicitly.

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

Usage Guidelines4/5

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

It tells the agent when the call is free (same domains/market within a day, or on Compare Domains) and lays out the escalation path when a call exceeds the workspace limit: ask the user, then retry with approvedMaxCostUsd. What's missing is a direct statement of when to prefer this over sibling history tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources