Skip to main content
Glama
Dweeb1578

Marketing Analytics MCP Server

by Dweeb1578

demo_report_save_week

Save a week's classified demo report to Supabase, including summary and per-lead data, without duplicates. Re-running same week converges and returns warnings if pipeline USD does not reconcile.

Instructions

Persist one week's classified demo report to Supabase (idempotent).

Upserts the week-summary row on week_ending and replaces that week's lead rows. Re-running a week converges — never duplicates. Returns a non-fatal warnings list if pipeline_usd does not reconcile with counted-inbound lead amounts (the week is still saved).

Args: week_summary_json: JSON object for one demo_report_weeks row. Required key: week_ending (YYYY-MM-DD, the Sunday). Other keys: week_start, total_inbound, unbranded, branded, direct, events, outbound_revivals, paid, flagged, ambiguous, ai_surface_leads, pipeline_usd, warnings, complete. leads_json: JSON array of per-lead rows. Each: deal_id, company, domain, classification, icp_fit, amount, dealstage, found_us, ai_surface_origin, hubspot_current_source, hubspot_update_to, rationale. week_ending is attached automatically.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
leads_jsonYes
week_summary_jsonYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description discloses idempotency, upsert behavior, lead row replacement, and non-fatal warnings for reconciliation issues. It does not cover auth or rate limits but adequately conveys core behavior.

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?

The description is front-loaded with purpose and efficiently explains key behaviors in ~10 sentences. The args section is detailed but necessary for clarity. No redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (2 params, output schema exists), the description covers the input structure, idempotent behavior, and result (warnings output). It is complete enough for an agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description adds extensive meaning: it details the required structure of week_summary_json (with required key week_ending and list of optional keys) and leads_json (array with per-lead fields). This fully compensates for the lack of schema descriptions.

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?

The description clearly states the tool persists a week's demo report to Supabase with idempotent upsert behavior. It uses a specific verb ('persist') and resource (one week's classified demo report). However, it does not explicitly differentiate from sibling tools like demo_report_datapack or demo_report_month_rollup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for saving a week's data but provides no guidance on when to use this tool versus alternatives or when not to use it. Context is clear but lacks exclusions or alternative suggestions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Dweeb1578/marketing-analytics-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server