MCP prompts and resources

This page is the technical reference for what your agent sees beyond Kreel’s tools when it connects over MCP: a fixed set of packaged prompts, and two resources. For a guided walkthrough of finding and using prompts, see the prompt library. For the tools themselves, see Data tools, Query, Brand context tools, and Publish a report.

MCP prompts

A prompt is not data. It is a parameterized message template: your agent fills in the arguments (if the prompt has any), sends the result as a chat message, and that message drives the agent to call the right Kreel tools in the right order. In an MCP client with native prompt support, such as Claude on web, desktop, or Cowork, a prompt appears by its title in the prompt picker. The name below is the identifier the prompt is registered under.

All prompt arguments are plain strings. Fill in a real value, such as a date or a brand name, when you use one.

| Name | Category | What it does | Arguments | |---|---|---|---| | weekly_report | Reporting | Produce a weekly performance report across all connected platforms. | week_of | | monthly_report | Reporting | Monthly cross-platform performance report with MoM comparison. | month | | country_breakdown | Reporting | Sales by country for a given period. | date_range | | product_breakdown | Reporting | Sales by product SKU for a given period. | date_range | | email_weekly_review | Reporting | Klaviyo email performance review - campaigns and flows. | week_of | | portfolio_pulse | Reporting | Cross-brand health check across your whole book of clients. | date_range | | daily_pulse | Health | Quick daily status check - spend pacing, delivery, learning phase. | none | | delivery_issues | Health | Look for delivery issues across ad platforms and Klaviyo. | none | | learning_phase_check | Health | Flag Meta ad sets stuck in learning phase. | none | | meta_account_audit | Audit | Structural audit of the Meta ad account. | none | | google_account_audit | Audit | Structural audit of the Google Ads account. | none | | creative_fatigue_check | Audit | Detect creative fatigue on active Meta ads. | none | | audience_saturation_review | Audit | Look for audience saturation signals on Meta ad sets. | none | | flow_performance_audit | Audit | Audit Klaviyo flow performance and delivery. | none | | scaling_candidates | Planning | Identify ads and campaigns ready to scale. | none | | budget_reallocation | Planning | Where to shift budget for maximum marginal ROAS. | none | | next_test_briefing | Planning | Brief the next creative batch based on current performance. | none | | onboard_brand | Onboarding | Build or extend a brand’s Knowledge Base through a data-informed interview. | none | | draft_meta_ads_from_folder | Drafts | Generate paste-ready Meta ad copy from local assets, without writing to Meta. | folder_path, campaign_objective | | draft_google_rsa | Drafts | Generate a paste-ready Google RSA, without writing to Google Ads. | brief | | draft_klaviyo_campaign | Drafts | Generate a paste-ready Klaviyo campaign, without writing to Klaviyo. | audience, subject_theme |

Brand selection

Every prompt above except portfolio_pulse checks whether it can reach more than one brand and asks the agent to pick one before continuing - the three draft_* prompts do this too, right after their no-write warning. portfolio_pulse is the only one with no brand-selection step: it works across your whole reach directly, pulling a portfolio-wide summary first, then drilling into any brand that needs attention by id afterward.

Drafts never touch the target platform

draft_meta_ads_from_folder, draft_google_rsa, and draft_klaviyo_campaign only read your data and draft copy. Each one ends with an explicit statement that nothing was created, uploaded, changed, or activated on Meta, Google, or Klaviyo.

onboard_brand is the one prompt that writes something: it walks the agent through updating the brand’s profile, positioning, competitors, and learnings. Those updates go through Kreel’s own write tools, so your MCP client may ask you to approve each one individually.

Use a prompt when your question matches one of the templates above: a reporting cadence, a health check, an audit, a planning decision, or a draft. For anything more specific, ask your agent directly, or point it at Data tools or Query.

MCP resources

Kreel’s MCP server exposes exactly two resources. A resource is reference data your agent can read to understand what it’s working with, not performance data itself.

kreel://schema

Provides: the JSON schema for the query DSL - every queryable table, its columns and computed fields, the supported operators (eq, ne, gt, gte, lt, lte, in, nin), and each table’s default and maximum row limits.

When an agent should use it: before calling query with a shape it hasn’t used before, or whenever it needs to know what is queryable outside the built-in tools like get_performance and get_entities.

kreel://platforms/{platform}/capabilities

{platform} is one of meta, google, klaviyo, or shopify.

Provides: a read/write capability list for that platform - what Kreel currently reads from it (for Meta, for example: campaigns, ad sets, ads, creatives, account- and campaign-level performance, and AI creative-intelligence tags), and whether Kreel writes anything back to it.

Every platform currently reports an empty write-capability list. Kreel reads Shopify, Meta, Google Ads, and Klaviyo; it does not write to any of them. The only things a Kreel agent can write are Kreel’s own data: the Brand Knowledge Base and hosted reports. For Google specifically, this resource also reflects whether Shopping and Performance Max asset-group data is currently syncing, since Kreel can turn that sync on or off independently of your other Google Ads data.

When an agent should use it: to check what a platform connection currently exposes before analyzing something specific to it, such as confirming creative-intelligence tags exist for Meta, or before assuming a write is possible on a connected platform.

For platform-specific setup and what actually syncs, see Shopify, Klaviyo, Meta Ads, and Google Ads.

Need help?

Email support@kreel.ai.