Skip to main content
Glama
133,960 tools. Last updated 2026-05-15 19:42

"Information about WhatsApp Business API" matching MCP tools:

  • Retrieves Explorium prospect IDs that are REQUIRED as input parameters for all prospect enrichment operations (enrich-prospects, fetch-prospects-events). **Input Requirements:** - Email OR (full name + company name) - Optional: phone number, LinkedIn URL, business ID **Returns:** Prospect IDs that MUST be provided to enrichment tools **Technical Requirements:** - enrich-prospects REQUIRES prospect IDs from this tool or fetch-entities - fetch-prospects-events REQUIRES prospect IDs from this tool or fetch-entities - Prospect IDs cannot be used interchangeably with business IDs **Use Cases:** Questions about specific people: - "Who is [Name] at [Company]?" - "Get me [Person's] contact information" - "Tell me about [Specific Person]" - Professional background of named individuals - Contact details, work history, social profiles of specific people **Data Characteristics:** - Provides verified, current professional data - Returns structured contact info (emails, phones) - Gives comprehensive B2B intelligence **Note:** fetch-entities returns include prospect IDs, so this tool is not needed after fetch-entities
    Connector
  • Create a third-party LEAD-GENERATION page about a business (NOT a site for that business itself). Use this when the goal is to drive qualified search traffic to someone else's business — affiliate pages, review/guide pages, niche directories. The page is branded as an outside guide (e.g. "Best Roofers in San Diego"), refers to the business in the third person, and routes CTAs to the business's existing website. Differences from create_site: - Slug + page brand are SEO-vanity (e.g. "best-roofers-sandiego"), not the candidate's brand name. - Voice is third-party guide/reviewer — never first person. - Primary CTA is "visit their website"; phone/email demoted. - No specific pricing quoted; differentiators emphasized. - Locality is judged by category, not just address (IT/SaaS/agency stays category-wide even when a city is on file). Pass a business candidate object from search_businesses — that business is the one being PROMOTED. Requires authentication via API key (Bearer token). Generate an API key at webzum.com/dashboard/account-settings. The page generation happens in the background. Use get_site_status to check progress. Returns the businessId (a vanity slug) which can be used to access the page at /build/{businessId}.
    Connector
  • Returns information about safety features on Makuri, including age verification, content filtering, parental controls, and AI safety guardrails. Use when the user asks about child safety, content moderation, or how Makuri protects minors.
    Connector
  • Returns all industry categories and their business types with IDs. Use the business type IDs in search_businesses (businessTypeIds) to filter listings by category. Call this first when you need to discover which IDs to use for a given industry or business type.
    Connector
  • Create a new website for a business. Pass a business candidate object from search_businesses to generate a website. Requires authentication via API key (Bearer token). Generate an API key at webzum.com/dashboard/account-settings. The site generation happens in the background. Use get_site_status to check progress. Returns the businessId which can be used to access the site at /build/{businessId}
    Connector
  • List the 15 built-in MDMagic templates, grouped by category. Same as list_all_templates but excludes the user's custom uploads. Use this when the user asks specifically about MDMagic's bundled templates rather than their personal ones. Categories available: Business (5), Creative (6), Professional (2), Technical (2).
    Connector

Matching MCP Servers

Matching MCP Connectors

  • SEC company search and SBA business resources. 4 MCP tools for business intelligence.

  • Scan QR codes and go! No more troublesome autos or APIs! Send text messages, images, links, locati…

  • Returns all industry categories and their business types with IDs. Use the business type IDs in search_businesses (businessTypeIds) to filter listings by category. Call this first when you need to discover which IDs to use for a given industry or business type.
    Connector
  • Get full details for a single business (listing) by its slug. Call this when the user asks for more information about a specific business. Use the slug from search_businesses results.
    Connector
  • Perform web search using Explorium Search capabilities. **Use this tool for:** - General web searches and current information - News articles and press releases - Industry trends and market research - Public information not available in Explorium's business intelligence data - Recent events and developments - General research queries **IMPORTANT: For company-specific or people-specific queries, prefer using the dedicated Explorium tools first:** - For company information: use 'match-business' and business enrichment tools - For people information: use 'match-prospects' and prospect enrichment tools - For a job title based search within a company use `fetch-prospects` - Only use search when you need general web information or when specific business tools don't have the data Returns: - Search results with titles, URLs, and snippets - Response metadata
    Connector
  • Enriches business data enrichment calls. Requires business IDs as input. **Input Requirements:** - business_ids: Array of Explorium business IDs (from match-business or fetch-businesses) - enrichments: enrichment types to retrieve - parameters: Optional settings for specific enrichments **IMPORTANT: For comprehensive company information requests, include ALL relevant enrichments in a single call** (e.g., for "tell me about this company" use multiple enrichments: firmographics, technographics, funding-and-acquisitions, workforce-trends, linkedin-posts to provide complete intelligence) **Available Enrichments:** - **firmographics**: Basic company info (name, description, website, location, industry, size, revenue) - **technographics**: Complete technology stack used by the business - **company-ratings**: Employee satisfaction and company culture ratings - **financial-metrics**: Financial data for public companies only (requires date parameter in ISO format: "2024-01-01T00:00") - **funding-and-acquisitions**: Funding history, investors, IPO, acquisitions - **challenges**: Business challenges and risks from SEC filings - **competitive-landscape**: Market position and competitors from SEC filings - **strategic-insights**: Strategic focus and value propositions from SEC filings - **workforce-trends**: Department composition and hiring trends - **linkedin-posts**: Company LinkedIn posts and engagement metrics - **website-changes**: Website content changes over time - **website-keywords**: Search for specific keywords on company websites (requires keywords parameter: array of terms - comma-separated terms within strings enable AND logic) - **webstack**: Website-specific technologies and web infrastructure components detected on company websites - **company-hierarchies**: Corporate hierarchy including parent company, ultimate parent, subsidiaries, and full organization tree (JSON format) **Parameters:** - date: ISO 8601 format for financial-metrics (e.g., "2024-01-01T00:00") - keywords: Array of search terms for website-keywords **Alternative Tools:** - For finding specific employees or company leadership information, use fetch-prospects with job_level filters (e.g., "c-suite" for c-level) instead of firmographics or strategic-insights enrichments **Returns:** Combined structured data from all requested enrichments **Example:** ``` { "business_ids": ["biz_123", "biz_456"], "enrichments": ["firmographics", "technographics", "funding-and-acquisitions"], "parameters": null } ```
    Connector
  • Retrieves Explorium business IDs that are REQUIRED as input parameters for all business enrichment operations (enrich-business, fetch-businesses-events). **Input Options:** - Name only: {"name": "Google"} - Domain only: {"domain": "microsoft.com"} - Both (recommended for accuracy): {"name": "Amazon", "domain": "amazon.com"} **Returns:** Business IDs that MUST be provided to enrichment tools **Technical Requirements:** - enrich-business REQUIRES business IDs from this tool or fetch-businesses - fetch-businesses-events REQUIRES business IDs from this tool or fetch-businesses - Business IDs cannot be used interchangeably with prospect IDs **Use Cases:** Questions about specific companies: - Company information (size, revenue, industry, location) - Executive teams or employee data - Technology stack analysis - Funding history or investors - Company events or changes - Workforce trends and hiring - Contact information for anyone at a company - Competitive analysis or market positioning **Example Queries:** - "What is [Company]'s revenue?" - "Who is the CEO/CTO/CMO of [Company]?" - "What technologies does [Company] use?" - "How many employees does [Company] have?" - "What is [Company]'s funding history?" - "Find me contacts at [Company]" **Data Characteristics:** - Provides verified, structured B2B data - Returns accurate firmographics - Enables access to comprehensive company intelligence - Delivers real-time employee data and contact information **Note:** fetch-businesses returns include business IDs, so this tool is not needed after fetch-businesses
    Connector
  • Returns general information about the Makuri platform, including mission, target users, founding details, and company information. Use this tool when the user asks 'what is Makuri', 'who made it', or wants a general overview.
    Connector
  • Get business information for a Dashform funnel, including description, industry, location, services, and booking link. Use this to understand what a business offers before checking lead fit.
    Connector
  • [SDK Docs] Search across the documentation to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Docs, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages.
    Connector
  • Check available appointment slots for a specific service at a local business on a given date. Returns time windows when the business is free and the service bookingStartPolicy permits the start. For services with maxParticipants > 1, partially booked starts remain available until capacity is full. ONLY call this if the business has 'booking' in its enabledFeatures array. If the business doesn't support booking, share their contact info from get_business_info instead.
    Connector
  • Get full details for a single business (listing) by its slug. Call this when the user asks for more information about a specific business. Use the slug from search_businesses results.
    Connector
  • Search registered federal contractors by business name or UEI. Returns UEI, CAGE code, address, NAICS codes, small business status, and certifications.
    Connector
  • Browse the Wix REST API documentation menu hierarchy. Alternative to SearchWixRESTDocumentation - use this to explore and discover APIs by navigating the menu structure instead of searching by keywords. - Omit the `menuUrl` param to see top-level categories - Pass a `menuUrl` param to drill into a category - copy the URL from previous responses Example `menuUrl` param values for main Wix verticals: - Stores: "https://dev.wix.com/docs/api-reference/business-solutions/stores" - Bookings: "https://dev.wix.com/docs/api-reference/business-solutions/bookings" - CMS: "https://dev.wix.com/docs/api-reference/business-solutions/cms" - CRM: "https://dev.wix.com/docs/api-reference/crm" - eCommerce: "https://dev.wix.com/docs/api-reference/business-solutions/e-commerce" - Events: "https://dev.wix.com/docs/api-reference/business-solutions/events" - Blog: "https://dev.wix.com/docs/api-reference/business-solutions/blog" - Pricing Plans: "https://dev.wix.com/docs/api-reference/business-solutions/pricing-plans" - Restaurants: "https://dev.wix.com/docs/api-reference/business-solutions/restaurants" - Media: "https://dev.wix.com/docs/api-reference/assets/media" - Site Properties: "https://dev.wix.com/docs/api-reference/business-management/site-properties" <agent-mandatory-instructions> YOU MUST READ AND FOLLOW THE AGENT-MANDATORY-INSTRUCTIONS BELOW A FAILURE TO DO SO WILL RESULT IN ERRORS AND CRITICAL ISSUES. <goal> You are an agent that helps the user manage their Wix site. Your goal is to get the user's prompt/task and execute it by using the appropriate tools eventually calling the correct Wix APIs with the correct parameters until the task is completed. </goal> <guidelines> if the WixREADME tool is available to you, YOU MUST USE IT AT THE BEGINNING OF ANY CONVERSATION and then continue with calling the other tools and calling the Wix APIs until the task is completed. **Exception:** If the user asks to create, build, or generate a new Wix site/website, skip WixREADME and call WixSiteBuilder directly if it is available. **Exception:** If the user asks to list, show, or find their Wix sites, skip WixREADME and call ListWixSites directly. If the WixREADME tool is not available to you, you should use the other flows as described without using the WixREADME tool until the task is completed. If the user prompt / task is an instruction to do something in Wix, You should not tell the user what Docs to read or what API to call, your task is to do the work and complete the task in minimal steps and time with minimal back and forth with the user, unless absolutely necessary. </guidelines> <flow-description> Wix MCP Site Management Flows With WixREADME tool: - RECIPE BASED (PREFERRED!): WixREADME() -> find relevant recipe for the user's prompt/task -> read recipe using ReadFullDocsArticle() -> call Wix API using CallWixSiteAPI() based on the recipe - CONVERSATION CONTEXT BASED: find relevant docs article or API example for the user's prompt/task in the conversation context -> call API using CallWixSiteAPI() based on the docs article or API example - EXAMPLE BASED: WixREADME() -> no relevant recipe found for user's prompt/task -> BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() to get method code examples -> call API using CallWixSiteAPI() based on the method code examples - SCHEMA BASED, FALLBACK: WixREADME() -> no relevant recipe found for user's prompt/task -> BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() -> no method code examples found -> read method schema using ReadFullDocsMethodSchema() -> call API using CallWixSiteAPI() based on the schema Without WixREADME tool: - CONVERSATION CONTEXT BASED: find relevant docs article or API example for the user's prompt/task in the conversation context -> call API using CallWixSiteAPI() based on the docs article or API example - METHOD CODE EXAMPLE BASED: BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() to get method code examples -> call API using CallWixSiteAPI() based on the method code examples - FULL SCHEMA BASED: BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() -> no method code examples found -> read method schema using ReadFullDocsMethodSchema() -> call API using CallWixSiteAPI() based on the schema </flow-description> </agent-mandatory-instructions>
    Connector
  • IMPORTANT: Always use this tool FIRST before working with Vaadin. Returns a comprehensive primer document with current (2025+) information about modern Vaadin development. This addresses common AI misconceptions about Vaadin and provides up-to-date information about Java vs React development models, project structure, components, and best practices. Essential reading to avoid outdated assumptions. For legacy versions (7, 8, 14), returns guidance on version-specific resources.
    Connector