Skip to main content
Glama
mambalabsdev

mcp-gtm-tech-stack-signal-scraper

by mambalabsdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Detect GTM Tech Stack

detect_gtm_tech_stack
Read-onlyIdempotent

Identify which GTM tools a company uses from its public website. Returns CRM, marketing automation, and sequencer signals as Clay-ready JSON boolean flags.

Instructions

Detect which GTM tools a company uses from its public-facing website. Returns CRM, sequencer, and marketing automation signals as a flat, Clay-ready JSON row, with per-tool boolean flags for HubSpot, Salesforce, Apollo, Gong, Intercom, and Marketo, plus a composite tech stack signal. Pass technologies to narrow the answer to named tools. Read-only; requires an APIFY_TOKEN and consumes Apify credits per call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoDeprecated alias for domain, accepted by the actor as a full company website URL. Prefer domain.
domainNoBare company domain without https:// and without a trailing slash. Example: stripe.com. Supply this, company_domain or url.
domainsNoA list of bare company domains to check in one run, one row per domain. The actor processes them in batches inside a single run, so a list costs one run start instead of one per domain. Use this or domain.
skipCacheNoBy default a clean detection is cached for 7 days and reused on repeat lookups, skipping the browser launch. Set true to force a fresh detection and ignore any cached result.
technologiesNoReport only these tools instead of every detectable one, which is how you answer "is this company using X". Only the ten tools with a client side fingerprint are selectable; Clay, Salesloft, Instantly and Lemlist leave no trace on a website and cannot be detected from one. Detection is unchanged either way, so a filtered call costs the same and reuses the same cache. Omit for every tool.
company_domainNoDeprecated alias for domain, accepted by the actor for older callers. Prefer domain.
crawl_additional_pagesNoIf true, crawls up to 2 additional pages per domain (pricing, product) to improve detection coverage. Slightly increases run time. Defaults to true when omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.0.6
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / company_domain
      Added value: +{
+  "description": "Deprecated alias for domain, accepted by the actor for older callers. Prefer domain.",
+  "type": "string"
+}
    • changedInput schema / properties / domain / description
      Previous value: -"Bare company domain without https:// and without a trailing slash. Example: stripe.com"New value: +"Bare company domain without https:// and without a trailing slash. Example: stripe.com. Supply this, company_domain or url."
    • addedInput schema / properties / domains
      Added value: +{
+  "description": "A list of bare company domains to check in one run, one row per domain. The actor processes them in batches inside a single run, so a list costs one run start instead of one per domain. Use this or domain.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / skipCache
      Added value: +{
+  "description": "By default a clean detection is cached for 7 days and reused on repeat lookups, skipping the browser launch. Set true to force a fresh detection and ignore any cached result.",
+  "type": "boolean"
+}
    • addedInput schema / properties / technologies
      Added value: +{
+  "description": "Report only these tools instead of every detectable one, which is how you answer \"is this company using X\". Only the ten tools with a client side fingerprint are selectable; Clay, Salesloft, Instantly and Lemlist leave no trace on a website and cannot be detected from one. Detection is unchanged either way, so a filtered call costs the same and reuses the same cache. Omit for every tool.",
+  "items": {
+    "enum": [
+      "hubspot",
+      "salesforce",
+      "marketo",
+      "pardot",
+      "intercom",
+      "drift",
+      "apollo",
+      "outreach",
+      "gong",
+      "zoominfo"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / url
      Added value: +{
+  "description": "Deprecated alias for domain, accepted by the actor as a full company website URL. Prefer domain.",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "domain"
-]
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's added value is the APIFY_TOKEN requirement, the per-call Apify credit consumption, and the return shape (flat Clay-ready JSON row with per-tool booleans). 'Read-only' merely restates readOnlyHint, but the auth and cost disclosures are genuinely additive.

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?

A single tight paragraph with purpose and return shape front-loaded, then usage and preconditions. Nearly every clause earns its place; the 'Read-only' phrase is the only redundant bit against the annotations.

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?

With no output schema, the description correctly explains the return value (flat JSON row, per-tool booleans, composite signal) and covers auth, cost, and the narrowing option. It does not state that at least one of domain/domains/url must be supplied, though the schema does, leaving only a minor gap.

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 description coverage is 100%, so all seven parameters are already documented, including the deprecation aliases, the 7-day cache, and the ten selectable fingerprints. The description's only parameter note ('Pass technologies to narrow the answer to named tools') repeats what the schema already states, so the baseline 3 applies.

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 — 'Detect which GTM tools a company uses from its public-facing website' — and enumerates the returned signals (CRM, sequencer, marketing automation) plus the specific tool flags. An agent knows exactly what this does without opening the schema.

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?

Gives concrete selection guidance for the key optional parameter ('Pass technologies to narrow the answer to named tools') and states the read-only + APIFY_TOKEN + credit-cost preconditions, which tells the agent when the call is appropriate. It stops short of explicit when-not-to-use or alternatives, but with no sibling tools there is little to route against.

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