Curated quick-look at 08Liter zeliter tables. Without arguments, lists the canonical CRM tables (B2B partner/brand/campaign + B2C member/liter/apply/review) with approximate row counts. With `table`, returns the column list and comments. Tables outside the curated set are still queryable via get_ddl + execute_read_sql. Read-only — no schema reveals secret data and the marketing send path remains B2B-only regardless of what you read.

curl -X POST http://localhost:3030/api/tools/describe_schema \
  -H "Authorization: Bearer crm_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"table":"brand"}'

await fetch('http://localhost:3030/api/tools/describe_schema', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer crm_YOUR_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
  "table": "brand"
}),
});

Full-schema introspection. Without arguments, lists every base table in the zeliter DB (primary CRM tables flagged + all others). With `table`, returns the CREATE TABLE DDL plus structured column/index metadata. Pair with execute_read_sql for ad-hoc analytics beyond the curated tools.

curl -X POST http://localhost:3030/api/tools/get_ddl \
  -H "Authorization: Bearer crm_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'

await fetch('http://localhost:3030/api/tools/get_ddl', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer crm_YOUR_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({}),
});

Run an ad-hoc read-only SQL query against the 08Liter zeliter DB. Any base table is queryable — including B2C tables (member, member_liter_transaction, campaign_apply, campaign_review, etc.) for analytics and reporting. Use get_ddl to discover tables/columns first. Row cap is applied to the FINAL output rows only by wrapping your query as `SELECT * FROM (<your sql>) AS t LIMIT N` — aggregations (SUM/COUNT/GROUP BY), JOINs, and ORDER BY run over the full underlying dataset, so totals stay correct regardless of the cap. Enforces: SELECT-class statements only (SELECT/WITH/SHOW/EXPLAIN/DESCRIBE), no semicolons, output rows clamped to MCP_MAX_ROW_LIMIT (10000 in production), query timeout, READ ONLY session. Every call is audit-logged with the executed SQL, returned column list, row count, and truncation flag.

curl -X POST http://localhost:3030/api/tools/execute_read_sql \
  -H "Authorization: Bearer crm_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'

await fetch('http://localhost:3030/api/tools/execute_read_sql', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer crm_YOUR_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({}),
});

08Liter canonical category tree. Use this to resolve numeric category_id values returned by search_brands into human-readable names, or to pick a category_id for scenario filtering. Top-level categories (parent_id=0) include 뷰티(12), 패션(13), 라이프(14), 식품(33), 유아(34), 취미(35), 반려동물(6666).

curl -X POST http://localhost:3030/api/tools/list_categories \
  -H "Authorization: Bearer crm_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"parentId":12,"language":"ko"}'

await fetch('http://localhost:3030/api/tools/list_categories', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer crm_YOUR_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
  "parentId": 12,
  "language": "ko"
}),
});

Search 08Liter brands (법인 회원의 마케팅 단위) with CRM-relevant filters. Returns brand identity, category, most-recent-campaign date, and a single contactable partner_admin (only when hasVerifiedContact=true). Always joins partner/partner_admin; never exposes unverified contacts. 'Brand' here means the 08L business entity — NOT a B2C member.

curl -X POST http://localhost:3030/api/tools/search_brands \
  -H "Authorization: Bearer crm_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"categoryId":12,"hasVerifiedContact":true,"lastCampaignBefore":"2025-01-01","limit":10}'

await fetch('http://localhost:3030/api/tools/search_brands', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer crm_YOUR_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
  "categoryId": 12,
  "hasVerifiedContact": true,
  "lastCampaignBefore": "2025-01-01",
  "limit": 10
}),
});

Drill into a single brand (법인 회원) with full CRM context: brand profile, parent partner, ALL verified contacts (not just one), N most-recent campaigns, and current liter balance from the latest deposit transaction. Use this after search_brands to build personalized outreach content.

curl -X POST http://localhost:3030/api/tools/get_brand \
  -H "Authorization: Bearer crm_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"brandId":12345,"recentCampaignsLimit":5}'

await fetch('http://localhost:3030/api/tools/get_brand', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer crm_YOUR_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
  "brandId": 12345,
  "recentCampaignsLimit": 5
}),
});

Search 08Liter campaigns with CRM-relevant filters. Returns campaign metadata plus the owning partner (법인 회원). Common status_codes: 1206=accepting, 1208=under review, 1209=closed/completed, 1210=cancelled, 1211=rejected. Use partnerId (obtained via search_brands) to scope to one brand owner.

curl -X POST http://localhost:3030/api/tools/search_campaigns \
  -H "Authorization: Bearer crm_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"statusCodes":["1209"],"minApplyCount":100,"limit":10}'

await fetch('http://localhost:3030/api/tools/search_campaigns', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer crm_YOUR_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
  "statusCodes": [
    "1209"
  ],
  "minApplyCount": 100,
  "limit": 10
}),
});

List ALL verified partner_admin contacts (법인 담당자) for a partner (법인 회원). Use this when you need to reach multiple contacts at one brand owner (e.g. CC the marketing team, reach out to multiple decision-makers). Every returned row is guaranteed to have a verified email and an active account.

curl -X POST http://localhost:3030/api/tools/search_partner_contacts \
  -H "Authorization: Bearer crm_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"partnerId":12345,"includeInactive":false}'

await fetch('http://localhost:3030/api/tools/search_partner_contacts', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer crm_YOUR_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
  "partnerId": 12345,
  "includeInactive": false
}),
});

Engagement snapshot for a single campaign: raw counts (view/apply/offer) plus derived ratios (fill rate, application density, oversubscription). Use this to pick high-performing campaigns for reference when drafting outreach, or to assess whether a partner (법인 회원) should be approached based on past traction.

curl -X POST http://localhost:3030/api/tools/get_campaign_performance \
  -H "Authorization: Bearer crm_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"campaignId":98765}'

await fetch('http://localhost:3030/api/tools/get_campaign_performance', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer crm_YOUR_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
  "campaignId": 98765
}),
});

List existing CRM segments stored in crm-pg. Use this to discover what target lists have already been created, before creating duplicates. Returns segment id, name, kind, target count, and creation info.

curl -X POST http://localhost:3030/api/tools/list_segments \
  -H "Authorization: Bearer crm_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"limit":10}'

await fetch('http://localhost:3030/api/tools/list_segments', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer crm_YOUR_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
  "limit": 10
}),
});

List existing email drafts in crm-pg with status, target count, and segment info. Use this to discover what campaigns are in progress before creating new ones.

curl -X POST http://localhost:3030/api/tools/list_drafts \
  -H "Authorization: Bearer crm_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"limit":10,"status":"in_review"}'

await fetch('http://localhost:3030/api/tools/list_drafts', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer crm_YOUR_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
  "limit": 10,
  "status": "in_review"
}),
});

List all dynamic menu groups and their items in the crm-web admin UI. Use this to discover existing menus before creating new ones, or to find the groupSlug/itemSlug needed for upsert_dynamic_page.

curl -X POST http://localhost:3030/api/tools/list_menu_groups \
  -H "Authorization: Bearer crm_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"includeFixed":false}'

await fetch('http://localhost:3030/api/tools/list_menu_groups', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer crm_YOUR_KEY',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
  "includeFixed": false
}),
});

Persist a named target list in crm-pg so later tools can reference it. Use this after a search_brands / search_partner_contacts / search_campaigns call to freeze the result set, then pass the returned segment_id to save_message_draft. Each target row captures the full snapshot for audit. kind=brand/partner means 법인 회원 단위, campaign means 캠페인 단위.

curl -X POST http://localhost:3030/api/tools/create_segment \
  -H "Authorization: Bearer crm_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"name":"dormant beauty 2026Q2","kind":"partner","targets":[{"externalId":12345,"snapshot":{"partner_name":"예시"}}]}'

await fetch('http://localhost:3030/api/tools/create_segment', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer crm_YOUR_KEY',
    'Content-Type': 'application/json',
    'Idempotency-Key': crypto.randomUUID(),
  },
  body: JSON.stringify({
  "name": "dormant beauty 2026Q2",
  "kind": "partner",
  "targets": [
    {
      "externalId": 12345,
      "snapshot": {
        "partner_name": "예시"
      }
    }
  ]
}),
});

Persist an AI-generated email campaign targeted at partner_admin (법인 담당자) with per-target rendering. Takes a segment_id plus a rendered message per target (subject + body + toEmail). Creates an EmailDraft in "draft" status — NOT sent. Reviewers will see it after queue_for_review is called. Always pass the exact toEmail you want to send to; the suppression list is checked at queue time, not here. B2C (일반 member) recipients are blocked upstream and must not appear here.

curl -X POST http://localhost:3030/api/tools/save_message_draft \
  -H "Authorization: Bearer crm_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"segmentId":"1","name":"2026Q2 dormant reactivation","subjectTemplate":"[08Liter] 재활성화 제안","bodyTemplate":"(본문)","targets":[{"externalId":12345,"toEmail":"admin@example.com","toName":"홍길동","subject":"[08Liter] {brand_name} 재활성화 제안","body":"..."}]}'

await fetch('http://localhost:3030/api/tools/save_message_draft', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer crm_YOUR_KEY',
    'Content-Type': 'application/json',
    'Idempotency-Key': crypto.randomUUID(),
  },
  body: JSON.stringify({
  "segmentId": "1",
  "name": "2026Q2 dormant reactivation",
  "subjectTemplate": "[08Liter] 재활성화 제안",
  "bodyTemplate": "(본문)",
  "targets": [
    {
      "externalId": 12345,
      "toEmail": "admin@example.com",
      "toName": "홍길동",
      "subject": "[08Liter] {brand_name} 재활성화 제안",
      "body": "..."
    }
  ]
}),
});

Hand a draft off to a human reviewer through the crm-web review gate. Transitions status draft -> in_review and sets queuedAt. The MCP server never sends email; after this call, the draft is visible at /drafts in crm-web and a reviewer approves or rejects per target. This is the hard gate between AI generation and outbound traffic.

curl -X POST http://localhost:3030/api/tools/queue_for_review \
  -H "Authorization: Bearer crm_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"draftId":"1","note":"please review by Fri"}'

await fetch('http://localhost:3030/api/tools/queue_for_review', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer crm_YOUR_KEY',
    'Content-Type': 'application/json',
    'Idempotency-Key': crypto.randomUUID(),
  },
  body: JSON.stringify({
  "draftId": "1",
  "note": "please review by Fri"
}),
});

Create a new top-level menu group in the crm-web admin UI header. Groups appear as tabs in the top navigation bar. Each group contains sidebar menu items (added via create_menu_item). Use this when the user asks to create a new section in the admin, e.g. "CRM 메뉴를 만들어줘".

curl -X POST http://localhost:3030/api/tools/create_menu_group \
  -H "Authorization: Bearer crm_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"name":"CRM","slug":"crm","icon":"📊","position":10}'

await fetch('http://localhost:3030/api/tools/create_menu_group', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer crm_YOUR_KEY',
    'Content-Type': 'application/json',
    'Idempotency-Key': crypto.randomUUID(),
  },
  body: JSON.stringify({
  "name": "CRM",
  "slug": "crm",
  "icon": "📊",
  "position": 10
}),
});

Add a sidebar menu item under an existing menu group. The item will appear in the left sidebar when its parent group is selected. For dynamic pages, leave href empty — the system generates /p/{groupSlug}/{itemSlug} automatically. Then call upsert_dynamic_page to define the page content.

curl -X POST http://localhost:3030/api/tools/create_menu_item \
  -H "Authorization: Bearer crm_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"groupSlug":"crm","name":"Dormant Brands","slug":"dormant"}'

await fetch('http://localhost:3030/api/tools/create_menu_item', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer crm_YOUR_KEY',
    'Content-Type': 'application/json',
    'Idempotency-Key': crypto.randomUUID(),
  },
  body: JSON.stringify({
  "groupSlug": "crm",
  "name": "Dormant Brands",
  "slug": "dormant"
}),
});

Create or update the content of a dynamic admin page. The page renders at /p/{groupSlug}/{itemSlug}. Sections define the page layout: "text" for HTML content, "stats" for metric cards, "table" for data tables. You can put search results from search_brands or search_campaigns directly into a table section's rows. Call this after create_menu_group + create_menu_item.

curl -X POST http://localhost:3030/api/tools/upsert_dynamic_page \
  -H "Authorization: Bearer crm_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"groupSlug":"crm","itemSlug":"dormant","title":"Dormant Brands","sections":[{"type":"text","body":"<h1>Dormant Brands</h1>"}]}'

await fetch('http://localhost:3030/api/tools/upsert_dynamic_page', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer crm_YOUR_KEY',
    'Content-Type': 'application/json',
    'Idempotency-Key': crypto.randomUUID(),
  },
  body: JSON.stringify({
  "groupSlug": "crm",
  "itemSlug": "dormant",
  "title": "Dormant Brands",
  "sections": [
    {
      "type": "text",
      "body": "<h1>Dormant Brands</h1>"
    }
  ]
}),
});