← Plugin catalog
Business & Operations

Data Bloo

Data Bloo P.C. v1.0.0

Analyze your marketing data

Create a free account to save this plugin.

From the developer

Not specified in the available declarations: capabilities, limitations, pricing & account requirements.

Onboarding example

Which Facebook Ads campaigns performed best in the last 30 days, and where should I improve?
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 15, 2026. Package observed Nov 15, 2026.

View package source →

Description

From the marketplace listing

Data Bloo helps you ask questions about your performance and get clear answers from your connected data sources. No exports, no spreadsheets, no manual reporting. Use it to check campaign performance, compare channels, spot trends, and summarize key takeaways for your team or clients. Data Bloo works with sources including Facebook Ads, LinkedIn Ads, TikTok Ads, Bing Ads, Google Search Console, Google Business Profile, Instagram Insights, Facebook Insights, WooCommerce, and more.

Language: English · Automatically detected from descriptions.

What changed

Files & skills

File archives

Plugin package2 files · 927 BytesBrowse files →
data-bloo-channel-analysis1 files · 2.69 KBBrowse files →
Skill instructions
data-bloo-channel-analysis6.75 KB

View saved version →

---
name: data-bloo-channel-analysis
description: Analyze one marketing, search, social, local, or ecommerce data source connected to Data Bloo. Use when a user selects a source such as Facebook Ads and asks for a performance analysis, trends, strongest and weakest results, or recommendations based on that source's data. Do not use for cross-channel comparisons or for creating, editing, pausing, publishing, or deleting external data.
---

# Data Bloo Channel Analysis

Use the Data Bloo MCP to analyze one connected data source and one selected account. All Data Bloo tools are read-only.

## Trigger conditions

Use this skill when the user asks to:

- Analyze one selected marketing, search, social, local, or ecommerce source.
- Review the performance of a source such as Facebook Ads.
- Identify trends, strongest and weakest campaigns, products, pages, posts, keywords, or other entities within one source.
- Summarize performance and provide practical recommendations based on connected data.
- Produce a detailed report for one source.

Do not use this skill when the user asks to:

- Compare two or more different channels or connectors.
- Create, edit, pause, publish, or delete campaigns, accounts, ads, dashboards, reports, or source data.
- Buy, upgrade, or manage a Data Bloo subscription.
- Give general marketing advice that does not require the user's connected Data Bloo data.
- Analyze a source that is not returned by `list_data_sources`.

## Workflow

### 1. Confirm the source

Identify the single data source the user wants to analyze.

If the source is not specified:

1. Call `list_data_sources`.
2. Present the available source names.
3. Ask the user to select one.

If the user names a source, call `list_data_sources` when needed to verify the current connector slug.

Never claim that a source is supported unless it is returned by `list_data_sources`.

### 2. Select the connected account

Call `get_connector_accounts` for the selected connector.

If more than one account is available:

1. Present the account names.
2. Ask the user which account to analyze.
3. Do not choose an account automatically.

If only one account is available, use it.

Use the `external_account_id` internally for tool calls. Do not display it unless required for troubleshooting.

Do not display authentication-owner names, OAuth scopes, token-expiry values, timestamps, or other internal connection metadata.

### 3. Resolve the date range

If the user gives explicit dates, use those dates.

If the user gives a supported relative period, call `get_dates` with the matching preset.

If the user gives no date range, call:

`get_dates` with `preset: "last_30_days"`

Use the returned `start_date` and `end_date`.

State the resolved date range in the final answer.

### 4. Discover valid fields

Call `list_fields` for the selected connector and account before calling `query_data`.

Select only field IDs returned by `list_fields`.

If the user names specific metrics or dimensions, use them when available.

If the user asks for a general analysis without specifying metrics, choose a balanced set of available fields appropriate for that source.

Examples, only when returned by `list_fields`:

- Advertising: impressions, clicks or link clicks, spend, CTR, CPC, leads, purchases, revenue, campaign name.
- Search performance: clicks, impressions, CTR, average position, query, page.
- Social insights: reach, impressions, engagement, followers, media or post.
- Ecommerce: revenue, orders, average order value, products, customers.
- Local performance: views, calls, direction requests, website actions.
- Website performance: performance score and Core Web Vitals.

Do not invent field IDs or assume that every connector supports the same metrics.

### 5. Query the selected source

Call `query_data` using:

- The verified connector slug.
- The selected account's `external_account_id`.
- Valid fields returned by `list_fields`.
- The resolved start and end dates.

For a general 

Preview of the first 4,000 characters. Read full instructions →

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package author
Data Bloo P.C.

Package observed Nov 15, 2026.

Technical details
First seen
Sep 30, 2026 · 22:02 UTC
Last seen
Nov 15, 2026 · 18:00 UTC
Collection status
Collected

plugin_asdk_app_6a3a620414088191b8c685ba8b344a7a

Download plugin data (JSON)

Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.