Skip to main content
Glama

strapi_list_blog_posts

Retrieve blog posts from Strapi CMS with filtering by status, category, author, tags, search, and sorting options.

Instructions

List all blog posts with advanced filtering, sorting, and pagination

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number
pageSizeNoResults per page
statusNoFilter by statusall
category_idNoFilter by category ID
author_idNoFilter by author ID
tag_idNoFilter by tag ID
sortNoSort field and direction (e.g., "publishedAt:desc", "title:asc")createdAt:desc
searchNoSearch in title and content

Implementation Reference

  • The main handler function that executes the strapi_list_blog_posts tool. It makes a GET request to Strapi's content-manager API for blog-posts with pagination parameters and returns the JSON response.
    async listBlogPosts (headers, args = {}) {
      const { page = 1, pageSize = 25, status = 'all' } = args
    
      const response = await axios.get(
        `${this.strapiUrl}/content-manager/collection-types/api::blog-post.blog-post`,
        {
          headers,
          params: {
            page,
            pageSize
          }
        }
      )
    
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(response.data, null, 2)
        }]
      }
    }
  • The input schema defining the parameters accepted by the strapi_list_blog_posts tool, including pagination, filtering, sorting, and search 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' },
        category_id: { type: 'number', description: 'Filter by category ID' },
        author_id: { type: 'number', description: 'Filter by author ID' },
        tag_id: { type: 'number', description: 'Filter by tag ID' },
        sort: { type: 'string', description: 'Sort field and direction (e.g., "publishedAt:desc", "title:asc")', default: 'createdAt:desc' },
        search: { type: 'string', description: 'Search in title and content' }
      }
    }
  • index.js:122-138 (registration)
    The tool registration in the ListTools response, including name, description, and input schema for strapi_list_blog_posts.
    {
      name: 'strapi_list_blog_posts',
      description: 'List all blog posts with advanced filtering, sorting, 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' },
          category_id: { type: 'number', description: 'Filter by category ID' },
          author_id: { type: 'number', description: 'Filter by author ID' },
          tag_id: { type: 'number', description: 'Filter by tag ID' },
          sort: { type: 'string', description: 'Sort field and direction (e.g., "publishedAt:desc", "title:asc")', default: 'createdAt:desc' },
          search: { type: 'string', description: 'Search in title and content' }
        }
      }
    },
  • index.js:368-370 (registration)
    The dispatch case in the CallToolRequest handler that routes to the listBlogPosts method for strapi_list_blog_posts.
    case 'strapi_list_blog_posts':
      return await this.listBlogPosts(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 mentions 'advanced filtering, sorting, and pagination,' which hints at read-only, non-destructive behavior, but doesn't explicitly state this is a safe read operation, describe potential rate limits, authentication needs, or what the return format looks like (e.g., array of posts). For a tool with 8 parameters and no annotations, this leaves significant gaps in understanding its behavior.

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 blog posts') and adds key features ('with advanced filtering, sorting, and pagination') without waste. Every word earns its place, making it easy to scan and understand quickly.

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

Completeness3/5

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

Given the tool's complexity (8 parameters, no output schema, no annotations), the description is adequate but incomplete. It covers the basic purpose and hints at functionality, but lacks details on behavioral traits (e.g., read-only nature, response format) and doesn't compensate for the missing output schema. For a list tool with filtering, more context on usage and results would be helpful, though the high schema coverage mitigates some gaps.

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 8 parameters with descriptions, defaults, and enums. The description adds minimal value beyond the schema by mentioning 'advanced filtering, sorting, and pagination,' which aligns with parameters like 'status', 'sort', 'page', and 'pageSize', but doesn't provide additional syntax, format details, or usage examples. Baseline 3 is appropriate as 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 ('List all blog posts') and resource ('blog posts'), which is specific and unambiguous. It distinguishes from sibling tools like 'strapi_get_blog_post' by indicating it returns multiple items rather than a single one. However, it doesn't explicitly differentiate from other list tools like 'strapi_list_events' or 'strapi_list_tutorials' beyond the resource name.

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

Usage Guidelines3/5

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

The description implies usage for retrieving multiple blog posts with filtering capabilities, suggesting it's for browsing or searching rather than fetching a single post. However, it lacks explicit guidance on when to use this versus alternatives like 'strapi_get_blog_post' (for single posts) or other list tools for different resources, and doesn't mention prerequisites or exclusions.

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