Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

B2B SaaS Affiliate & Partner Program Finder

find_b2b_affiliate_partner_programs
Read-onlyIdempotent

Discover B2B affiliate and partner programs on SaaS or e-commerce domains, returning program platforms, commission percentages, and partnership contacts for outreach.

Instructions

Discover PartnerStack, Impact, Rewardful, FirstPromoter, Tolt, commission percentages, and partnership 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": "find_b2b_affiliate_partner_programs"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYesSaaS or e-commerce domains

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 establish readOnly/openWorld/idempotent/non-destructive, so the safety profile is covered. The description adds genuine extra context — what fields come back and the price point ($0.80/1k) — but says nothing about coverage limits, behavior for domains with no detected program, or result cardinality.

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 efficient sentence that front-loads the concrete data sources and appends cost at the end where it belongs. No filler, though the comma-separated vendor list is dense and could be a parenthetical to improve scannability.

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?

For a one-parameter, read-only lookup with no output schema and full annotation coverage, the description covers what is retrieved and at what cost. It stops short of telling the agent what a result looks like per domain or how to interpret a miss, which is the main remaining 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?

With a single parameter at 100% schema description coverage, the schema already carries the semantics ('SaaS or e-commerce domains'). The description adds little beyond timing/scope, and it slightly narrows the notion to 'SaaS domains' only, omitting the e-commerce case the schema allows.

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?

Uses a specific verb ('Discover') with a concrete resource set: named partner platforms (PartnerStack, Impact, Rewardful, FirstPromoter, Tolt), commission percentages, and partnership contacts, scoped to SaaS domains. The intersection of vendors and fields makes it clearly distinct from generic lead-scraping siblings, though it never explicitly contrasts itself with any of 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?

No when-to-use or when-not-to-use guidance, no preconditions (e.g. domain must have a public partner page), and no pointer to alternatives like the company dossier or competitor pricing tools. The only implicit usage signal is that you supply domains.

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