B2Brilliant MCP Server

discover_business

Analyze a business from its website URLs to uncover key details, branding, and competitors, enabling informed outreach and campaign creation.

Instructions

Discover and analyze a target business from website URLs

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": {
      "urls": "<urls>"
    },
    "name": "discover_business"
  }
}

Input Schema

Name	Required	Description	Default
`urls`	Yes	Array of target business website URLs to analyze
`options`	No	Additional discovery options

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether the tool is read-only, whether it fetches external data, what side effects exist, or what the output will be. The options (deepSearch, findBranding, findCompetitors) hint at behavior but are not explained in the description.

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?

The description is a single, concise sentence with no redundant information. It efficiently communicates the core purpose, though it could be slightly more specific without adding much length.

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

Completeness2/5

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

The tool performs a potentially complex task (discovering and analyzing businesses from URLs) but the description gives no indication of expected outputs, prerequisites, or limitations. With no output schema and no annotations, the one-line description is insufficient for an agent to fully understand the tool's capabilities or invocation results.

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?

The input schema provides complete descriptions for all parameters (100% coverage), so the baseline is 3. The description adds context that the URLs are for a 'target business', but otherwise does not enrich the parameter meaning beyond what the schema already states.

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 uses specific verbs ('Discover and analyze') and identifies the resource ('a target business from website URLs'), making its primary function clear. However, it does not explicitly differentiate from sibling tools like discover_user_business, though the phrasing implies a general target rather than a user-specific one.

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 guidance on when to use this tool versus alternatives. No mention of when to choose discover_business over discover_user_business or refine_business, nor any exclusions or prerequisites.

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

Deploy Server