Skip to main content
Glama

kadi_bence/tech-stack-detector

kadi_bence--tech-stack-detector
Destructive

This tool calls the Actor "kadi_bence/tech-stack-detector" and retrieves its output results. Actor description: $1.50 per 1,000 websites. Detect the technology stack of websites (Wappalyzer/BuiltWith alternative). Input: URLs or domains; optional category filter. Returns per site: CMS, ecommerce, analytics, frameworks, CDN, server and payment processors with versions and confidence, from 7,600+ fingerprints.

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": "kadi_bence--tech-stack-detector"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsNoWebsites to analyse: a JSON list like ["example.com", "https://example.com/shop"], or one string ("example.com", or several separated by commas or new lines). https:// is added when missing (with fallbacks to www. and http://). Duplicates are skipped. Max 100,000 per run. Also accepted under the aliases url, startUrls (strings or {"url": ...} objects), domains, domain, websites, website. Example values: ["https://apify.com","wordpress.org","www.allbirds.com","vercel.com","www.bbc.com"]
waitSecsNoMax seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget.
minConfidenceNoHide technologies detected with a lower confidence score. Most detections are 100; weaker signals (e.g. a generic script name) score 25-75. Example: 75 for a stricter list.
maxConcurrencyNoHow many websites are analysed at the same time. Each website is still fetched politely (robots.txt, crawl-delay). Example: 20-50 for large lists. Example values: 10
onlyCategoriesNoReturn only technologies in these categories, e.g. CMS, Ecommerce, Analytics. Leave empty for all 100+ categories. Sites with nothing found in your categories are not charged.
includeEvidenceNoAdd up to 5 "evidence" strings per technology showing what matched (header, script URL, meta tag, cookie...), e.g. scriptSrc: https://cdn.shopify.com/... Useful to audit detections; makes the dataset bigger.
includeVersionsNoAdd the version number when the site exposes it (e.g. WordPress 7.2, jQuery 3.6.0). Example values: true
maxPagesPerSiteNo1 = only the URL you give (usually the homepage), fastest. 2-10 = also analyse a few same-site pages linked from it (pricing, shop, blog...), which finds tools that are loaded only on inner pages. You still pay once per website. Example: 3 Example values: 1
proxyConfigurationNoUsually not needed. If some sites answer 403 "blocked", you can try Apify Proxy (datacenter). Residential proxies are not supported. Example values: {"useApifyProxy":false}
requestTimeoutSecsNoGive up on a slow website after this many seconds (one retry on 429/5xx answers). Pages are read up to 3 MB. Example values: 20

Output Schema

NameRequiredDescriptionDefault
tipNoAdvisory guidance RAG Web Browser wrote to its key-value store under the reserved "TIP" key
runIdYesActor run ID
statsNoRun statistics
statusYesRun status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED
actorIdYesStable Apify Actor ID from the run record
summaryYesPast-tense summary of the run state
exitCodeNoActor process exit code; populated for terminal states (especially FAILED)
nextStepYesOne primary follow-up action with identifiers interpolated
storagesYesDataset and key-value store metadata, keyed by alias. "default" is always the primary entry.
actorNameNo"username/actor-name"
startedAtNoISO timestamp when the run started
finishedAtNoISO timestamp when the run finished (terminal states only)
statusMessageNoPass-through from Apify run.statusMessage
apifyConsoleUrlNoPersonalized Apify Console link to the run; present only for Console sessions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema
      Added value: +{
      +  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
      +  "properties": {
      +    "advertising": {
      +      "items": {},
      +      "type": "array"
      +    },
      +    "analytics": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "cdn": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "cms": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "description": {
      +      "type": "string"
      +    },
      +    "domain": {
      +      "type": "string"
      +    },
      +    "ecommerce": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "error": {
      +      "type": "null"
      +    },
      +    "finalUrl": {
      +      "type": "string"
      +    },
      +    "framework": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "hosting": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "language": {
      +      "type": "string"
      +    },
      +    "liveChat": {
      +      "items": {},
      +      "type": "array"
      +    },
      +    "marketingAutomation": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "pagesAnalyzed": {
      +      "type": "number"
      +    },
      +    "paymentProcessors": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "programmingLanguages": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "scrapedAt": {
      +      "type": "string"
      +    },
      +    "server": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "status": {
      +      "type": "number"
      +    },
      +    "tagManagers": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "technologies": {
      +      "items": {
      +        "properties": {
      +          "categories": {
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "confidence": {
      +            "type": "number"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "version": {
      +            "type": [
      +              "null",
      +              "string"
      +            ]
      +          },
      +          "website": {
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "technologyCount": {
      +      "type": "number"
      +    },
      +    "technologyNames": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "title": {
      +      "type": "string"
      +    },
      +    "url": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already flag openWorldHint and destructiveHint, and the description adds genuinely useful context: the per-website price and what each result contains (CMS, ecommerce, analytics, CDN, etc. with versions and confidence). It omits run lifecycle behavior — that the call starts an Actor run that may be capped and need polling — leaving the schema to carry that.

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 dense sentences: the boilerplate 'calls the Actor and retrieves its output results' is low-value, but the Actor description that follows front-loads cost, purpose, inputs and outputs efficiently.

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

Completeness4/5

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

For a 10-parameter scraping actor with a full output schema and fully described inputs, the description covers purpose, pricing and return shape adequately. The only real gap is not flagging the async/polling pattern, which is documented in the waitSecs parameter instead.

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 all ten parameters are already documented in detail. The description only echoes two of them (the URL input and the optional category filter) plus the version/confidence notion, adding little beyond the schema.

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+resource — 'Detect the technology stack of websites' — and positions it against well-known references (Wappalyzer/BuiltWith alternative). Among siblings like pagespeed-checker, seo-site-audit and sitemap-extractor, the technology-detection scope is unmistakable.

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?

Gives the accepted input shape ('URLs or domains; optional category filter') and a pricing signal ($1.50 per 1,000 websites) that helps an agent judge cost. It never says when to prefer this over a sibling audit tool or when detection is inappropriate, so guidance stays implicit.

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.