strapi-plugin-ai-sdk 0.6.8 → 0.6.9

package/dist/server/index.js

@@ -297,7 +297,7 @@ const searchContentSchema = zod.z.object({
     'The content type UID to search, e.g. "api::article.article" or "plugin::users-permissions.user"'
   ),
   query: zod.z.string().optional().describe("Full-text search query string (searches across all searchable text fields)"),
-  filters: zod.z.record(zod.z.string(), zod.z.unknown()).optional().describe('Strapi filter object, e.g. { username: { $containsi: "john" } }'),
+  filters: zod.z.record(zod.z.string(), zod.z.unknown()).optional().describe('Strapi filter object. Scalar: { title: { $containsi: "hello" } }. Relation: { author: { name: { $eq: "John" } } }. ManyToMany: { contentTags: { title: { $eq: "tutorial" } } }. Operators: $eq, $ne, $containsi, $in, $gt, $lt, $gte, $lte, $null, $notNull.'),
   fields: zod.z.array(zod.z.string()).optional().describe("Specific fields to return. If omitted, returns all fields (large content fields stripped unless includeContent is true)."),
   sort: zod.z.string().optional().describe('Sort order, e.g. "createdAt:desc"'),
   page: zod.z.number().optional().default(1).describe("Page number (starts at 1)"),
@@ -307,7 +307,7 @@ const searchContentSchema = zod.z.object({
   populate: zod.z.union([zod.z.string(), zod.z.array(zod.z.string()), zod.z.record(zod.z.string(), zod.z.unknown())]).optional().describe('Relations to populate. Defaults to "*" (all). Can be a string, array, or object.'),
   includeContent: zod.z.boolean().optional().default(false).describe("When true, includes large content fields (content, blocks, body, etc.) in results. Default false to reduce context size.")
 });
-const searchContentDescription = 'Search and query any Strapi content type. Use listContentTypes first to discover available content types and their fields, then use this tool to query specific collections. Use sort (e.g. "createdAt:desc") and pageSize: 1 to get the latest entry. By default, large content fields are stripped from results — set includeContent to true or use fields to get full content.';
+const searchContentDescription = 'Search and query any Strapi content type. Use listContentTypes first to discover available content types and their fields, then use this tool to query specific collections. Use sort (e.g. "createdAt:desc") and pageSize: 1 to get the latest entry. By default, large content fields are stripped from results — set includeContent to true or use fields to get full content. To filter by a relation, nest the filter: { relationField: { fieldOnRelation: { $operator: "value" } } }.';
 function stripLargeFields(obj) {
   const stripped = {};
   for (const [key, value] of Object.entries(obj)) {
@@ -706,7 +706,7 @@ const aggregateContentSchema = zod.z.object({
   operation: zod.z.enum(["count", "countByField", "countByDateRange"]).describe(
     "count — total count; countByField — group by a field; countByDateRange — bucket by date"
   ),
-  filters: zod.z.record(zod.z.string(), zod.z.unknown()).optional().describe('Strapi filter object, e.g. { category: { name: "tech" } }'),
+  filters: zod.z.record(zod.z.string(), zod.z.unknown()).optional().describe('Strapi filter object. Scalar: { title: { $containsi: "hello" } }. Relation: { author: { name: { $eq: "John" } } }. ManyToMany: { contentTags: { title: { $eq: "tutorial" } } }.'),
   groupByField: zod.z.string().optional().describe('Field to group by for countByField. Just use the field name — relation fields are auto-resolved to their display name (e.g. "author", "category"). You can also use dot paths like "author.email" for a specific sub-field.'),
   dateField: zod.z.string().optional().default("createdAt").describe('Date field for countByDateRange (default: "createdAt")'),
   granularity: zod.z.enum(["day", "week", "month"]).optional().default("month").describe("Bucket granularity for countByDateRange"),
@@ -2193,8 +2193,26 @@ function describeTools(tools) {
   return `Available tools:
 ${lines.join("\n")}`;
 }
-const DEFAULT_PREAMBLE = 'You are a Strapi CMS assistant. Use your tools to fulfill user requests. When asked to create or update content, use the appropriate tool — do not tell the user you cannot. When performing bulk operations (e.g. publish multiple items), call multiple tools in parallel in a single step rather than one at a time.\n\nFor analytics and counting questions (e.g. "how many", "count", "distribution", "trends", "breakdown"), use the aggregateContent tool instead of searchContent — it is faster and purpose-built for these queries. Present analytics results as markdown tables. After showing analytics results, suggest 2-3 follow-up questions the user might find useful under a "**You might also want to know:**" heading.';
-const DEFAULT_PUBLIC_PREAMBLE = 'You are a helpful public assistant for this website. Use your tools to answer questions about the site content. You cannot modify any content or perform administrative actions.\n\nFor analytics and counting questions (e.g. "how many", "count", "distribution", "trends", "breakdown"), use the aggregateContent tool instead of searchContent — it is faster and purpose-built for these queries. Present analytics results as markdown tables. After showing analytics results, suggest 2-3 follow-up questions the user might find useful under a "**You might also want to know:**" heading.';
+const DEFAULT_PREAMBLE = `You are a Strapi CMS assistant. Use your tools to fulfill user requests. When asked to create or update content, use the appropriate tool — do not tell the user you cannot. When performing bulk operations (e.g. publish multiple items), call multiple tools in parallel in a single step rather than one at a time.
+
+For analytics and counting questions (e.g. "how many", "count", "distribution", "trends", "breakdown"), use the aggregateContent tool instead of searchContent — it is faster and purpose-built for these queries. Present analytics results as markdown tables. After showing analytics results, suggest 2-3 follow-up questions the user might find useful under a "**You might also want to know:**" heading.
+
+Strapi filter syntax for searchContent and aggregateContent:
+- Scalar fields: { title: { $containsi: "hello" } }
+- Relation (manyToOne): { author: { name: { $eq: "John" } } }
+- Relation (manyToMany): { contentTags: { title: { $eq: "tutorial" } } }
+- Always nest relation filters as: { relationField: { fieldOnRelatedType: { $operator: value } } }
+- Never use flat dot-path syntax like "contentTags.title" in filters — always use nested objects.`;
+const DEFAULT_PUBLIC_PREAMBLE = `You are a helpful public assistant for this website. Use your tools to answer questions about the site content. You cannot modify any content or perform administrative actions.
+
+For analytics and counting questions (e.g. "how many", "count", "distribution", "trends", "breakdown"), use the aggregateContent tool instead of searchContent — it is faster and purpose-built for these queries. Present analytics results as markdown tables. After showing analytics results, suggest 2-3 follow-up questions the user might find useful under a "**You might also want to know:**" heading.
+
+Strapi filter syntax for searchContent and aggregateContent:
+- Scalar fields: { title: { $containsi: "hello" } }
+- Relation (manyToOne): { author: { name: { $eq: "John" } } }
+- Relation (manyToMany): { contentTags: { title: { $eq: "tutorial" } } }
+- Always nest relation filters as: { relationField: { fieldOnRelatedType: { $operator: value } } }
+- Never use flat dot-path syntax like "contentTags.title" in filters — always use nested objects.`;
 function composeSystemPrompt(config2, toolsDescription, override) {
   const base = override || config2?.systemPrompt || DEFAULT_PREAMBLE;
   if (base.includes("{tools}")) {

package/dist/server/index.mjs

@@ -277,7 +277,7 @@ const searchContentSchema = z.object({
     'The content type UID to search, e.g. "api::article.article" or "plugin::users-permissions.user"'
   ),
   query: z.string().optional().describe("Full-text search query string (searches across all searchable text fields)"),
-  filters: z.record(z.string(), z.unknown()).optional().describe('Strapi filter object, e.g. { username: { $containsi: "john" } }'),
+  filters: z.record(z.string(), z.unknown()).optional().describe('Strapi filter object. Scalar: { title: { $containsi: "hello" } }. Relation: { author: { name: { $eq: "John" } } }. ManyToMany: { contentTags: { title: { $eq: "tutorial" } } }. Operators: $eq, $ne, $containsi, $in, $gt, $lt, $gte, $lte, $null, $notNull.'),
   fields: z.array(z.string()).optional().describe("Specific fields to return. If omitted, returns all fields (large content fields stripped unless includeContent is true)."),
   sort: z.string().optional().describe('Sort order, e.g. "createdAt:desc"'),
   page: z.number().optional().default(1).describe("Page number (starts at 1)"),
@@ -287,7 +287,7 @@ const searchContentSchema = z.object({
   populate: z.union([z.string(), z.array(z.string()), z.record(z.string(), z.unknown())]).optional().describe('Relations to populate. Defaults to "*" (all). Can be a string, array, or object.'),
   includeContent: z.boolean().optional().default(false).describe("When true, includes large content fields (content, blocks, body, etc.) in results. Default false to reduce context size.")
 });
-const searchContentDescription = 'Search and query any Strapi content type. Use listContentTypes first to discover available content types and their fields, then use this tool to query specific collections. Use sort (e.g. "createdAt:desc") and pageSize: 1 to get the latest entry. By default, large content fields are stripped from results — set includeContent to true or use fields to get full content.';
+const searchContentDescription = 'Search and query any Strapi content type. Use listContentTypes first to discover available content types and their fields, then use this tool to query specific collections. Use sort (e.g. "createdAt:desc") and pageSize: 1 to get the latest entry. By default, large content fields are stripped from results — set includeContent to true or use fields to get full content. To filter by a relation, nest the filter: { relationField: { fieldOnRelation: { $operator: "value" } } }.';
 function stripLargeFields(obj) {
   const stripped = {};
   for (const [key, value] of Object.entries(obj)) {
@@ -686,7 +686,7 @@ const aggregateContentSchema = z.object({
   operation: z.enum(["count", "countByField", "countByDateRange"]).describe(
     "count — total count; countByField — group by a field; countByDateRange — bucket by date"
   ),
-  filters: z.record(z.string(), z.unknown()).optional().describe('Strapi filter object, e.g. { category: { name: "tech" } }'),
+  filters: z.record(z.string(), z.unknown()).optional().describe('Strapi filter object. Scalar: { title: { $containsi: "hello" } }. Relation: { author: { name: { $eq: "John" } } }. ManyToMany: { contentTags: { title: { $eq: "tutorial" } } }.'),
   groupByField: z.string().optional().describe('Field to group by for countByField. Just use the field name — relation fields are auto-resolved to their display name (e.g. "author", "category"). You can also use dot paths like "author.email" for a specific sub-field.'),
   dateField: z.string().optional().default("createdAt").describe('Date field for countByDateRange (default: "createdAt")'),
   granularity: z.enum(["day", "week", "month"]).optional().default("month").describe("Bucket granularity for countByDateRange"),
@@ -2173,8 +2173,26 @@ function describeTools(tools) {
   return `Available tools:
 ${lines.join("\n")}`;
 }
-const DEFAULT_PREAMBLE = 'You are a Strapi CMS assistant. Use your tools to fulfill user requests. When asked to create or update content, use the appropriate tool — do not tell the user you cannot. When performing bulk operations (e.g. publish multiple items), call multiple tools in parallel in a single step rather than one at a time.\n\nFor analytics and counting questions (e.g. "how many", "count", "distribution", "trends", "breakdown"), use the aggregateContent tool instead of searchContent — it is faster and purpose-built for these queries. Present analytics results as markdown tables. After showing analytics results, suggest 2-3 follow-up questions the user might find useful under a "**You might also want to know:**" heading.';
-const DEFAULT_PUBLIC_PREAMBLE = 'You are a helpful public assistant for this website. Use your tools to answer questions about the site content. You cannot modify any content or perform administrative actions.\n\nFor analytics and counting questions (e.g. "how many", "count", "distribution", "trends", "breakdown"), use the aggregateContent tool instead of searchContent — it is faster and purpose-built for these queries. Present analytics results as markdown tables. After showing analytics results, suggest 2-3 follow-up questions the user might find useful under a "**You might also want to know:**" heading.';
+const DEFAULT_PREAMBLE = `You are a Strapi CMS assistant. Use your tools to fulfill user requests. When asked to create or update content, use the appropriate tool — do not tell the user you cannot. When performing bulk operations (e.g. publish multiple items), call multiple tools in parallel in a single step rather than one at a time.
+
+For analytics and counting questions (e.g. "how many", "count", "distribution", "trends", "breakdown"), use the aggregateContent tool instead of searchContent — it is faster and purpose-built for these queries. Present analytics results as markdown tables. After showing analytics results, suggest 2-3 follow-up questions the user might find useful under a "**You might also want to know:**" heading.
+
+Strapi filter syntax for searchContent and aggregateContent:
+- Scalar fields: { title: { $containsi: "hello" } }
+- Relation (manyToOne): { author: { name: { $eq: "John" } } }
+- Relation (manyToMany): { contentTags: { title: { $eq: "tutorial" } } }
+- Always nest relation filters as: { relationField: { fieldOnRelatedType: { $operator: value } } }
+- Never use flat dot-path syntax like "contentTags.title" in filters — always use nested objects.`;
+const DEFAULT_PUBLIC_PREAMBLE = `You are a helpful public assistant for this website. Use your tools to answer questions about the site content. You cannot modify any content or perform administrative actions.
+
+For analytics and counting questions (e.g. "how many", "count", "distribution", "trends", "breakdown"), use the aggregateContent tool instead of searchContent — it is faster and purpose-built for these queries. Present analytics results as markdown tables. After showing analytics results, suggest 2-3 follow-up questions the user might find useful under a "**You might also want to know:**" heading.
+
+Strapi filter syntax for searchContent and aggregateContent:
+- Scalar fields: { title: { $containsi: "hello" } }
+- Relation (manyToOne): { author: { name: { $eq: "John" } } }
+- Relation (manyToMany): { contentTags: { title: { $eq: "tutorial" } } }
+- Always nest relation filters as: { relationField: { fieldOnRelatedType: { $operator: value } } }
+- Never use flat dot-path syntax like "contentTags.title" in filters — always use nested objects.`;
 function composeSystemPrompt(config2, toolsDescription, override) {
   const base = override || config2?.systemPrompt || DEFAULT_PREAMBLE;
   if (base.includes("{tools}")) {

package/dist/server/src/tool-logic/search-content.d.ts

@@ -16,7 +16,7 @@ export declare const searchContentSchema: z.ZodObject<{
     populate: z.ZodOptional<z.ZodUnion<readonly [z.ZodString, z.ZodArray<z.ZodString>, z.ZodRecord<z.ZodString, z.ZodUnknown>]>>;
     includeContent: z.ZodDefault<z.ZodOptional<z.ZodBoolean>>;
 }, z.core.$strip>;
-export declare const searchContentDescription = "Search and query any Strapi content type. Use listContentTypes first to discover available content types and their fields, then use this tool to query specific collections. Use sort (e.g. \"createdAt:desc\") and pageSize: 1 to get the latest entry. By default, large content fields are stripped from results \u2014 set includeContent to true or use fields to get full content.";
+export declare const searchContentDescription = "Search and query any Strapi content type. Use listContentTypes first to discover available content types and their fields, then use this tool to query specific collections. Use sort (e.g. \"createdAt:desc\") and pageSize: 1 to get the latest entry. By default, large content fields are stripped from results \u2014 set includeContent to true or use fields to get full content. To filter by a relation, nest the filter: { relationField: { fieldOnRelation: { $operator: \"value\" } } }.";
 export interface SearchContentParams {
     contentType: string;
     query?: string;

package/package.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.6.8",
+  "version": "0.6.9",
   "keywords": [
     "strapi",
     "strapi-plugin",