List blog posts, case studies, or resources. Returns published and unpublished items unless filtered.

Fetch the full record (all fields, including body content) for a single blog post, case study, or resource by slug or id.

Create a new blog post, case study, or resource. Provide a JSON object matching the table's columns. blog_posts: slug, title, excerpt, content, author, date, category, read_time, published, meta_title, meta_description, og_image, image_url. case_studies: slug, title, industry, summary, challenge, solution, results (string array), metrics (JSON array of {label, value}), published, meta_title, meta_description, og_image, image_url. resources: slug, title, type ('Whitepaper'|'Research'|'Documentation'|'Case Study'), description, file_url, featured, published.

Update fields on an existing blog post, case study, or resource. Identify the row by slug or id, and pass only the fields you want to change.

Toggle the published flag on a blog post, case study, or resource. Optionally set a future publish_at timestamp for scheduled publishing (blog_posts and case_studies only).

Permanently delete a blog post, case study, or resource by slug. This cannot be undone — confirm with the user before calling.

List all career/job postings, optionally filtered to published-only.

Create a new job posting on the careers page.

Update fields on an existing job posting, identified by id.

Permanently delete a job posting. Prefer unpublishing (update_job_posting with published: false) if you just want to close applications while keeping history.

List applications submitted for job postings. Filter by career_id or status. Status is typically one of: new, reviewing, interviewing, offered, rejected, hired (site-defined, not enforced by DB).

Update the status of a job application (e.g. move a candidate to 'interviewing').

List inbound consultation/demo requests submitted via the site's contact form. Filter by status (e.g. 'new', 'replied', 'closed' — site-defined).

Fetch a single consultation request along with its internal notes thread.

Update a consultation request's status and/or admin_notes. Use add_inquiry_note instead if you want to append a timestamped note rather than overwrite admin_notes.

Append an internal note to a consultation request's thread (does not overwrite prior notes).

List email newsletter subscribers, most recent first.

List past newsletter campaigns that were sent, with subject, sent/failed counts, and timestamps.

Per-content-item view counts, average time on page, average scroll depth, and last-viewed timestamp, across blog posts, case studies, and resources. Sorted by view count descending.

Automated content performance categorization: top-performing ('stellar'), recently trending ('improving'), and stale/underperforming content, each with a suggested next action.

Daily page-view counts and unique session counts over a trailing window.

Total count of distinct visitors tracked across all time.

Visitor breakdown by dimension (e.g. device_type, browser, os, country) with counts per value.

Conversion counts and rates by conversion type (e.g. newsletter signup, consultation request) derived from tracked content views.

Paginated raw page-view events with full detail: session, device, browser, os, country, city, referrer, scroll depth, time on page, and any conversion. Use for drill-down investigation; prefer the summary tools for regular reporting.

Recent admin actions taken across the site (content edits, publishes, etc.), most recent first.

Send a newsletter campaign to all subscribers via the site's send-newsletter function (Resend). This actually dispatches real emails — confirm the subject and HTML content with the user before calling.

Send an email reply to someone who submitted a consultation/demo request, via the site's reply-consultation function. This sends a real email to the requester and marks the request as replied. Confirm the message with the user before calling.