Data Bloo

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 channel analysis, include a useful breakdown dimension when available, such as campaign, ad set, post, query, page, product, or date.

Do not request more fields than needed for a clear analysis.

### 6. Analyze the results

Evaluate only the returned data.

Look for:

- Overall performance.
- Strongest and weakest entities.
- Meaningful differences or trends.
- Efficiency metrics where available.
- Missing, zero, or unusual values.
- Opportunities supported by the data.

Do not infer causation when the data only shows correlation.

Do not calculate or compare currency values unless the currency context is clear.

### 7. Handle missing data safely

If the query returns no rows or an error:

1. Explain that no data was returned for the selected source, account, and period.
2. Ask the user before changing the date range, account, or requested fields.
3. Do not silently widen the period or substitute another account.

### 8. Present the result

By default, provide:

1. A compact performance table.
2. A short summary of the main findings.
3. Practical recommendations based only on the returned data.

A recommended structure is:

## Channel overview
A short summary of the selected source, account, and date range.

## Performance table
Use clear metric columns and an appropriate breakdown.

## Key findings
Highlight the most important results, trends, strengths, and weaknesses.

## Recommendations
Give practical, read-only recommendations supported by the data.

If the user asks for more detail, expand the response with:

- Executive summary
- Overall performance
- Performance by campaign, content, product, query, page, or other available dimension
- Trends
- Strongest and weakest results
- Data limitations
- Detailed recommendations

### 9. Recommendations

Recommendations must:

- Be directly supported by the returned data.
- Explain the observation behind each recommendation.
- Remain advisory and read-only.
- Never claim that Data Bloo changed a campaign, account, budget, dashboard, or source setting.

Use cautious wording when the data is incomplete or a metric definition is unclear.

## Additional tool rules

Use `list_accounts` only when a broader overview of all connected sources is necessary.

Use `get_user` only when:

- The user asks about their Data Bloo plan, MCP access, usage limits, or remaining calls.
- A tool response indicates that access or usage limits may prevent the requested analysis.

Do not use `get_user` as part of a normal channel analysis.

## Output quality rules

- Analyze only one connector at a time.
- Use plain language.
- Keep the default response concise.
- Clearly name the source, account, and date range.
- Separate facts from recommendations.
- Mention missing or unavailable metrics.
- Do not expose unnecessary internal identifiers or authentication metadata.
- Do not promote subscriptions, pricing, upgrades, or checkout links.