Skip to main content
Glama

Visibility Genies

Find sites using a technology

find_sites_using_technology

A reverse tech stack lookup for prospect lists: the strongest sites in one country that run a technology (a CMS, shop platform, analytics or other tool), each with its title, domain rank (a 0 to 1,000 link-graph score), language and when the crawler last visited it. Estimated price: up to $0.27, one request for up to 100 sites, billed by the sites returned. The same technology and country saved within 30 days is read free, and it opens free on Domain Overview's Tech stack tab. 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>",
      "technology": "<technology>",
      "countryCode": "<countryCode>"
    },
    "name": "find_sites_using_technology"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
technologyYesA technology as tech stacks name it, e.g. 'WordPress', 'Shopify' or 'HubSpot'.
countryCodeYesTwo letter country code the sites are in, e.g. 'US' or 'NL'.
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
domainsNo
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?

Despite sparse annotations, the description discloses the full behavioral envelope: per-call cost estimate up to $0.27, billing by sites returned, the 30-day cached-read exemption, the workspace agent spend limit and how it is held and charged, and the refusal-then-retry-with-approvedMaxCostUsd flow. That is exactly the kind of spend and failure behavior an agent needs before invoking a paid, non-read-only 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 purpose and result fields are front-loaded, followed by cost, caching, and spend-limit mechanics in a logical order. It is longer than most definitions, and the approvedMaxCostUsd explanation is partly duplicated between the description and the schema, which keeps it from a 5.

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?

For a paid, open-world lookup, everything an agent needs to call it correctly is present: required inputs, per-call cost ceiling, cache behavior, spend-limit handling, and the refusal/approval recovery path. Return values are redundantly listed even though an output schema exists, but that adds convenience rather than confusion.

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 baseline is 3, but the description adds real meaning beyond the schema by tying the returned-site count to billing and by explaining that the technology-plus-country pair drives the 30-day free read. The approvedMaxCostUsd retry condition is also restated with the user-approval requirement, reinforcing rather than merely repeating the 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?

The description names a specific verb and resource ('reverse tech stack lookup') and states scope precisely: strongest sites in one country that run a given technology, with the fields returned per site. It implicitly separates itself from site-anchored lookups in the sibling list, but it never explicitly names an alternative tool to contrast with, so it falls short of a 5.

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 gives a clear use context ('for prospect lists') and the exact filtering axes (one technology, one country), plus the cost-saving note that a repeat of the same technology and country within 30 days is free and already visible on the Domain Overview Tech stack tab. There is no explicit when-not guidance or named alternative tool, so it stops at 4.

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