Skip to main content
Glama

SteadyScrape Company Data

Websites using a technology

sites_using_technology
Read-only

Lists company websites that use the named technologies (all of them) or any tool in a category, e.g. Shopify, HubSpot, Klaviyo, Stripe, Intercom. Filter by country, language, niche keywords and domain rank (0-1000 authority score). Returns domain, title, country, domain rank, matched technologies, key stack columns (e-commerce, CMS, CRM, payments, marketing automation, analytics, chat), company social pages and when the technology was last seen. Billed per domain returned plus a run start fee.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sites_using_technology"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDomains to return (default 20, max 50). Billed per domain returned.
sort_byNoDefault domain_rank_desc (biggest first).
keywordsNoOptional niche words matched in the site title or description, e.g. coffee, skincare.
countriesNoOptional 2-letter country codes, e.g. US, GB, DE.
languagesNoOptional 2-letter language codes, e.g. en, de.
technologiesNo1-5 technology names; a site must use all of them. E.g. Shopify, Klaviyo.
max_domain_rankNoSkip sites above this domain rank, e.g. 500 for smaller businesses.
min_domain_rankNoSkip sites below this domain rank, e.g. 150.
last_seen_within_daysNoOnly sites where the technology was seen in the last N days (default 365).
technology_categoriesNoAlternatively or additionally: sites using any tool in these categories.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuinely non-structured context: per-domain billing plus a run start fee, and the composition of returned records (matched technologies and stack columns), which an agent needs before choosing a limit. No rate limits or pagination behavior are disclosed.

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

Conciseness5/5

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

Two dense sentences, purpose and matching logic front-loaded before filters, then return contents and cost. Every clause conveys information an agent would otherwise have to infer; nothing is repeated from the schema or annotations.

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 10-parameter tool with no output schema, the description supplies what is missing: the shape of returned records, the cost model, and the inclusive-vs-any matching rule. Nothing essential for correct invocation is absent.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents every parameter including defaults, bounds, and enum values. The description adds only a light gloss, reframing domain rank as a 0-1000 authority score and giving sample technology and category inputs. Baseline 3 applies when the schema carries the parameter burden.

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

Purpose5/5

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

States a specific verb and resource ('Lists company websites') plus the exact matching semantics: all named technologies (AND) or any tool in a category (OR). The example technology names (Shopify, HubSpot, Klaviyo, Stripe, Intercom) make the resource concrete, and no sibling in the supplied set is a competing site-listing tool.

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?

Clarifies the choice between 'technologies' (site must use all of them) and 'technology_categories' (any tool in the category), which is the main selection ambiguity for this tool, and frames filters as narrowing criteria. It stops short of explicit when-not or alternative-tool guidance, and the 'get_results' sibling is never referenced.

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