Skip to main content
Glama
sec-edgar-fda-b2b-mcp

sec-edgar-fda-b2b-mcp

enrich_b2b_websites

Read-onlyIdempotent

Turn company domains into actionable B2B sales leads by retrieving verified emails, phone numbers, social links, and detected tech stacks.

Instructions

Enrich B2B company websites with verified contact emails, phone numbers, social links, and tech stack.

Use this tool to turn a list of company domains into actionable B2B sales leads.
Returns a JSON array of up to 25 enriched profiles containing website, emails, phones,
socialLinks (LinkedIn, X, GitHub), and detected techStack. Requires the APIFY_TOKEN environment variable.

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": {
      "websites": "<websites>"
    },
    "name": "enrich_b2b_websites"
  }
}

Input Schema

NameRequiredDescriptionDefault
websitesYesList of full B2B company website URLs to enrich (e.g., ['https://linear.app', 'https://supabase.com']).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / websites / description
      Added value: +"List of full B2B company website URLs to enrich (e.g., ['https://linear.app', 'https://supabase.com'])."
  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, openWorld, non-destructive), so the description only needs to add context — and it does: a hard cap of 25 profiles per response and a required APIFY_TOKEN environment variable, both of which materially affect how an agent batches calls. It does not mention rate limits, credit/cost consumption of the underlying actor, or what happens for unresolvable domains.

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?

Front-loaded with the operation and its outputs, then usage context, then the return shape and auth requirement — a sensible ordering with no repeated information. Minor waste in the marketing phrasing 'actionable B2B sales leads', which conveys little operational signal.

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 one-parameter batch enrichment tool this is nearly complete: batch cap, auth prerequisite, and output contents are all stated, and an output schema exists so return-field detail is redundant anyway. The remaining gaps (cost per run, behavior on failed domains, whether results are cached) are secondary but worth naming for a paid third-party actor.

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 parameter with 100% schema description coverage, including concrete URL examples, so the schema already carries the semantics. The description restates 'a list of company domains' without adding format details beyond that; 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 ('Enrich B2B company websites') and enumerates the enrichment outputs: verified contact emails, phone numbers, social links, and tech stack. Nothing in the sibling list operates on company domains, so the tool is trivially distinguishable from the SEC/FDA/Shopify/YC retrieval tools.

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?

The second sentence gives clear usage context ('turn a list of company domains into actionable B2B sales leads'), which is enough to know when to reach for it. It stops short of naming exclusions or alternatives — e.g. there is no guidance for single-domain lookups or for what to do when a domain is already known to be enriched.

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