Plotline

List all Plotline products (apps) the authenticated user has access to. Returns each product's ID and name. Call this tool FIRST before any other tool — you need a product ID for all other operations. Returns: { products: [{ id, name }] }

list_products

Analyze activity and performance for one authorized product using read-only SQL. First read plotline://skills/analytics and relevant schemas using get_plotline_knowledge; search_plotline_knowledge finds metric definitions and joins. Supports joins, CTEs, subqueries and aggregations. Use {name:Type} parameters for values. Queries are automatically restricted to the selected product. Results include columns, rows and queryId; requests exceeding limits return an error without partial results.

Check a proposal made with propose_changes: status (PROPOSED, APPLIED, REJECTED, STALE, EXPIRED, SUPERSEDED), the reviewer's comment, and why it went stale. A STALE proposal means the data changed after it was proposed: read the documents again and propose again.

Read a complete Plotline knowledge document or schema by registered ID or plotline:// URI. Start with plotline://guide or search_plotline_knowledge. Returns content and versions, equivalent to native resources/read. Use the registered IDs or plotline:// URIs returned by search.

Propose edits for a person to review and approve in the Plotline dashboard. NOTHING is changed until someone approves it there. Supported today: AI Director objectives (decisioningObjectives): create, edit setup (Strategy brief = `statement`, Guardrails = `strategy`, goal events, audience, holdout/rollout), delete, and add/rename/move/remove topics and subtopics; and a subtopic's SMS, email or push copy (aiDirectorContent): add, edit or remove variants, or create the content for a subtopic that has none. Push variants have title, body and optional Android subtitle (plain text; image and deeplink are kept; a new push variant may copyFromSlot to reuse a sibling's image and deeplink). Email variants have subject, preheader and the text of the layout's blocks (read them with read_object on aiDirectorContent); a new email variant needs copyFromSlot or templateId. New copy is saved as Draft unless the reviewer also approves it for sending; approved email is re-rendered after approval. And AI Director signals (decisioningSignals): create, edit (name, question, answer type, options, audience, evaluation windows, attribute key, default value, schedule) and delete; publishing and pausing stay in the dashboard. And SQL segments (cohorts): create, edit (name, description, sqlDefinition.query, sqlDefinition.description) and delete a segment whose members are a ClickHouse SELECT returning UserRefID. Test the SQL with analytics_query first and write sqlDefinition.description in plain words; read plotline://knowledge/recipes/sql-segment. Filter segments made in the dashboard can't be changed here. Before the first call, read plotline://knowledge/recipes/propose-changes with get_plotline_knowledge; read current documents with read_object so patches target real ids. Send one user intent per proposal (many changes are fine). Use dryRun:true to check without saving. Returns {status, changeSetId?, reviewUrl?, summary, issues[]}: status INVALID means nothing was saved; fix each error (it has path and hint) and call again. When saved, share the reviewUrl with the user and say it is waiting for their approval. To revise a pending proposal, pass supersedes=<changeSetId>.

Read product objects: event definitions, attributes, campaigns, steps, journeys, segments (cohorts: SQL segments have definitionType SQL and sqlDefinition.query/description), AI Director objectives (decisioningObjectives: topics/subtopics are embedded in intentSets), AI Director signals (decisioningSignals: a question the model answers per user, saved to a signal_* user attribute), rendered email bodies (emailContentDocuments), the product's email layouts (emailTemplates: project {title:1,source:1}; content is large) and aiDirectorContent: a subtopic's copy as the flat view propose_changes edits (SMS text; push title and body; email subject, preheader and layout blocks as plain text; filter on stored fields such as parentCampaignId, type, aiDirector.intentId; no projection). For AI Director, first read plotline://knowledge/recipes/ai-director-objective (signals: plotline://knowledge/recipes/ai-director-signal). Fetch one with filter {_id: {$oid: id}}, limit 1, or list using filters, projection, sorting and pagination. Read plotline://skills/object-read and plotline://schema/objects/<collection> through get_plotline_knowledge for fields and filter examples. Access is automatically restricted to the selected product. Returns {collection,items,hasMore,nextSkip?} using Extended JSON for typed values. Read-only; no aggregation pipelines or cross-collection joins.

Search Plotline's analytics reference: table and object schemas, metrics, relationships and SQL examples. Returns IDs, resource URIs, snippets and versions; fetch relevant documents with get_plotline_knowledge or resources/read. These references describe how to read and interpret data; they contain no customer records.