How to build a read-later list with Grok

Set up a read-later list for me in databasedmcp, in one go.

1. Create a database called reading, described as "Read-later list: links, why I saved them, tags, and what I thought after reading".
2. Create two tables:
   - links: id, url (required, unique), title (required), site, why (my reason for saving it, in my words), minutes (rough reading time, if I give one), status (unread, read or dropped, defaults to unread), verdict (what I thought once I've read it), added_at (defaults to now), read_at (NULL until I've read it).
   - tags: link_id (references links), tag (lowercase, reused), with one row per link and tag.
3. Write the database a guide that says what each table is for, to check a URL isn't already saved before adding it, and to check the existing tags before inventing a new one. Include the queries for "something to read now": up to five unread links that fit in the minutes I have, oldest first, and "by tag": the links with a given tag, newest first.

From then on: when I give you a link, save it with the title, the site and my reason, and tag it. When I say I've read something, set it to read with read_at and my verdict. When I say I'm not going to read it, set it to dropped. Show me the tables when you're finished.

CREATE TABLE links (
  id INTEGER PRIMARY KEY,
  url TEXT NOT NULL UNIQUE,
  title TEXT NOT NULL,
  site TEXT,
  why TEXT,
  minutes INTEGER,
  status TEXT NOT NULL DEFAULT 'unread' CHECK (status IN ('unread', 'read', 'dropped')),
  verdict TEXT,
  added_at TEXT NOT NULL DEFAULT CURRENT_TIMESTAMP,
  read_at TEXT
);

CREATE TABLE tags (
  link_id INTEGER NOT NULL REFERENCES links(id),
  tag TEXT NOT NULL,
  PRIMARY KEY (link_id, tag)
);

# reading: links to read later

- **links**: one per URL. `why` is my reason for saving it, in my words. `minutes` is a rough reading time if I gave one. status: unread, read, dropped. `verdict` is what I thought once read.
- **tags**: one row per link and tag, lowercase, reused (pricing, sqlite, design). Check existing tags before inventing one.

Check the URL isn't already saved before adding it.

Something to read now: `SELECT id, title, minutes, why FROM links WHERE status = 'unread' AND minutes <= ? ORDER BY added_at LIMIT 5`

By tag: `SELECT l.id, l.title, l.status FROM links l JOIN tags t ON t.link_id = l.id WHERE t.tag = ? ORDER BY l.added_at DESC`

INSERT INTO links (url, title, site, why, minutes) VALUES (?, ?, ?, ?, ?) RETURNING id
-- params: ["https://www.sqlite.org/whentouse.html","Appropriate uses for SQLite","sqlite.org","For the architecture doc: when SQLite is enough.",15]

INSERT INTO tags (link_id, tag) SELECT ?, value FROM json_each(?)
-- params: [1,"[\"sqlite\",\"architecture\"]"]

INSERT INTO links (url, title, site, why, minutes) VALUES (?, ?, ?, ?, ?) RETURNING id
-- params: ["https://www.w3.org/WAI/fundamentals/accessibility-intro/","Introduction to web accessibility","w3.org","Before the signup form redesign.",10]

UPDATE links SET status = 'read', read_at = datetime('now'), verdict = ? WHERE id = ?
-- params: ["Good. The section on server-side use settles the question for the architecture doc.",1]

SELECT id, title, minutes, why FROM links WHERE status = 'unread' AND minutes <= ? ORDER BY added_at LIMIT 5
-- params: [10]

SELECT l.id, l.title, l.status, l.verdict FROM links l JOIN tags t ON t.link_id = l.id WHERE t.tag = ? ORDER BY l.added_at DESC
-- params: ["sqlite"]

SELECT strftime('%Y-%m', added_at) AS month, count(*) AS saved, sum(status = 'read') AS read, sum(status = 'unread') AS still_unread FROM links GROUP BY month ORDER BY month DESC