Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

Zapier, Make.com & n8n Integration Ecosystem Spy

spy_zapier_make_n8n_integrations
Read-onlyIdempotent

Detect public webhooks, REST API docs, Zapier apps, Make modules, n8n nodes, and developer relations contacts on SaaS domains to identify integration opportunities and outreach targets.

Instructions

Detect public webhooks, REST API docs, Zapier apps, Make modules, n8n nodes, and developer relations contacts on SaaS domains ($0.80/1k).

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

Input Schema

NameRequiredDescriptionDefault
domainsYesSaaS domains to inspect

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds a genuinely useful non-annotation detail, the pricing rate ($0.80/1k), but says nothing about result granularity, coverage limits per domain, or whether misses are reported, so behavioral context remains thin beyond annotations.

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?

One front-loaded sentence with the verb first and the target list before the price, with no filler. The parenthetical pricing could arguably be its own line but it does not obscure the purpose.

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

Completeness3/5

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

With no output schema and a one-parameter input, the description should convey what an agent gets back or how results differ per target type; the artifact enumeration hints at it but never states the return shape or per-domain limits. It is adequate to decide whether to call the tool, but not fully complete.

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?

There is a single required parameter with 100% schema description coverage ('SaaS domains to inspect'), so the schema already carries the semantics. The description adds nothing about accepted domain formats or batch size limits, leaving it at the baseline for a fully documented 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 concrete verb ('Detect') and enumerates the specific artifacts it looks for: webhooks, REST API docs, Zapier apps, Make modules, n8n nodes, and dev-rel contacts on SaaS domains. That makes the resource and scope unambiguous and clearly separates it from the sibling spies that target stores, job boards, or review sites, though it never explicitly contrasts itself with them.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of when a different sibling (e.g. extract_saas_competitor_pricing_matrix or scrape_g2_capterra_software_reviews) would be the better pick. The agent must infer the use case entirely from the artifact list.

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