Skip to main content
Glama

strapi_create_tutorial

Create step-by-step tutorials in markdown format for Strapi CMS, including title, content, difficulty levels, and metadata for organized learning content.

Instructions

Create a new tutorial with step-by-step content in markdown

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTutorial title
contentYesTutorial content in MARKDOWN format
descriptionNoShort description
difficultyNoDifficulty level
durationNoEstimated duration in minutes
author_idYesAuthor ID
category_idNoCategory ID
tag_idsNoArray of tag IDs
publishedAtNoPublication date (ISO 8601) or null for draft

Implementation Reference

  • The handler function that executes the tool logic by constructing a data payload from input arguments and making a POST request to Strapi's content-manager API endpoint for tutorials.
    async createTutorial (headers, args) {
      const data = {
        title: args.title,
        content: args.content,
        description: args.description,
        difficulty: args.difficulty,
        duration: args.duration,
        author: args.author_id,
        category: args.category_id,
        tags: args.tag_ids,
        publishedAt: args.publishedAt || null
      }
    
      const response = await axios.post(
        `${this.strapiUrl}/content-manager/collection-types/api::tutorial.tutorial`,
        data,
        { headers }
      )
    
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(response.data, null, 2)
        }]
      }
    }
  • Input schema definition for the strapi_create_tutorial tool, specifying parameters, types, descriptions, and required fields.
    name: 'strapi_create_tutorial',
    description: 'Create a new tutorial with step-by-step content in markdown',
    inputSchema: {
      type: 'object',
      properties: {
        title: { type: 'string', description: 'Tutorial title' },
        content: { type: 'string', description: 'Tutorial content in MARKDOWN format' },
        description: { type: 'string', description: 'Short description' },
        difficulty: { type: 'string', enum: ['beginner', 'intermediate', 'advanced'], description: 'Difficulty level' },
        duration: { type: 'number', description: 'Estimated duration in minutes' },
        author_id: { type: 'number', description: 'Author ID' },
        category_id: { type: 'number', description: 'Category ID' },
        tag_ids: { type: 'array', items: { type: 'number' }, description: 'Array of tag IDs' },
        publishedAt: { type: 'string', description: 'Publication date (ISO 8601) or null for draft' }
      },
      required: ['title', 'content', 'author_id']
    }
  • index.js:390-391 (registration)
    Switch case in the CallToolRequest handler that dispatches to the createTutorial method for this tool.
    case 'strapi_create_tutorial':
      return await this.createTutorial(headers, request.params.arguments)
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool creates a tutorial but doesn't mention whether this is a draft or published by default, what permissions are required, how errors are handled, or what the response looks like (e.g., returns the created tutorial object). For a mutation tool with zero annotation coverage, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that states the core purpose without unnecessary words. It's appropriately sized and front-loaded with the essential action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a creation tool with 9 parameters, no annotations, and no output schema, the description is incomplete. It doesn't address behavioral aspects like default states (draft vs. published), error conditions, or response format, leaving significant gaps for an AI agent to understand how to use it effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all 9 parameters thoroughly. The description adds minimal value by specifying 'step-by-step content in markdown' (which aligns with the schema's 'content' description) but doesn't provide additional context beyond what's in the structured fields. Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Create a new tutorial') and specifies the content format ('step-by-step content in markdown'), which distinguishes it from generic creation tools. However, it doesn't explicitly differentiate from sibling creation tools like 'strapi_create_blog_post' or 'strapi_create_event' beyond the resource type.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing author_id), when to choose this over 'strapi_create_blog_post', or how it relates to sibling tools like 'strapi_publish_tutorial' or 'strapi_update_tutorial'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AINative-Studio/ainative-strapi-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server