Skip to main content
Glama

strapi_list_tutorials

Retrieve tutorials from Strapi CMS with filtering by status, difficulty, category, and pagination controls for organized content discovery.

Instructions

List all tutorials with filtering and pagination

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number
pageSizeNoResults per page
statusNoFilter by statusall
difficultyNoFilter by difficulty
category_idNoFilter by category ID
sortNoSort field and directioncreatedAt:desc

Implementation Reference

  • The handler function that implements the core logic of 'strapi_list_tutorials' by querying the Strapi CMS API for tutorials with pagination support.
    async listTutorials (headers, args = {}) {
      const { page = 1, pageSize = 25 } = args
    
      const response = await axios.get(
        `${this.strapiUrl}/content-manager/collection-types/api::tutorial.tutorial`,
        {
          headers,
          params: {
            page,
            pageSize
          }
        }
      )
    
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(response.data, null, 2)
        }]
      }
    }
  • Input schema defining the parameters accepted by the 'strapi_list_tutorials' tool, including pagination, status, difficulty, category, and sorting options.
    inputSchema: {
      type: 'object',
      properties: {
        page: { type: 'number', description: 'Page number', default: 1 },
        pageSize: { type: 'number', description: 'Results per page', default: 25 },
        status: { type: 'string', enum: ['published', 'draft', 'all'], description: 'Filter by status', default: 'all' },
        difficulty: { type: 'string', enum: ['beginner', 'intermediate', 'advanced'], description: 'Filter by difficulty' },
        category_id: { type: 'number', description: 'Filter by category ID' },
        sort: { type: 'string', description: 'Sort field and direction', default: 'createdAt:desc' }
      }
    }
  • index.js:222-236 (registration)
    Tool registration in the ListToolsRequestSchema response, defining name, description, and input schema.
    {
      name: 'strapi_list_tutorials',
      description: 'List all tutorials with filtering and pagination',
      inputSchema: {
        type: 'object',
        properties: {
          page: { type: 'number', description: 'Page number', default: 1 },
          pageSize: { type: 'number', description: 'Results per page', default: 25 },
          status: { type: 'string', enum: ['published', 'draft', 'all'], description: 'Filter by status', default: 'all' },
          difficulty: { type: 'string', enum: ['beginner', 'intermediate', 'advanced'], description: 'Filter by difficulty' },
          category_id: { type: 'number', description: 'Filter by category ID' },
          sort: { type: 'string', description: 'Sort field and direction', default: 'createdAt:desc' }
        }
      }
    },
  • index.js:393-394 (registration)
    Dispatch registration in the CallToolRequestSchema switch statement that routes execution to the listTutorials handler.
    case 'strapi_list_tutorials':
      return await this.listTutorials(headers, request.params.arguments)
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it mentions 'filtering and pagination', it doesn't describe key behaviors like whether this is a read-only operation, what the return format looks like, error conditions, rate limits, or authentication requirements. For a list tool with 6 parameters and no annotations, this leaves significant gaps in understanding how the tool behaves.

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 front-loads the core purpose ('List all tutorials') and adds qualifying details ('with filtering and pagination'). There's no wasted verbiage or redundant information, making it appropriately concise for the tool's complexity.

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?

Given the tool has 6 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., structure of tutorial objects), error handling, or behavioral constraints. For a list operation with multiple filtering options, more context is needed to use it effectively without trial and error.

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 6 parameters with descriptions, defaults, and enums. The description adds minimal value by mentioning 'filtering and pagination' which loosely relates to some parameters but doesn't provide additional semantic context beyond what's in the schema. This meets the baseline for high schema coverage.

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 verb ('List') and resource ('tutorials'), specifying the action and target. It also mentions 'filtering and pagination' which adds useful scope. However, it doesn't explicitly distinguish this tool from sibling list tools like 'strapi_list_blog_posts' or 'strapi_list_events', which have similar functionality for different resources.

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 when to choose this over other list tools (e.g., for tutorials specifically) or when to use filtering/pagination features. There's no context about prerequisites, exclusions, or comparisons with sibling tools.

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