Skip to main content
Glama

strapi_create_event

Create new events in Strapi CMS by specifying title, description, type, dates, and location for webinars, workshops, meetups, or conferences.

Instructions

Create a new event (webinar, workshop, meetup, conference)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesEvent title
descriptionYesEvent description in MARKDOWN
event_typeYesType of event
start_dateYesEvent start date/time (ISO 8601)
end_dateNoEvent end date/time (ISO 8601)
locationNoPhysical location or virtual platform
registration_urlNoRegistration/signup URL
max_attendeesNoMaximum number of attendees
publishedAtNoPublication date (ISO 8601) or null for draft

Implementation Reference

  • The main handler function that executes the tool logic: constructs event data from arguments and sends a POST request to Strapi's event collection endpoint to create the event.
    async createEvent (headers, args) {
      const data = {
        title: args.title,
        description: args.description,
        event_type: args.event_type,
        start_date: args.start_date,
        end_date: args.end_date,
        location: args.location,
        registration_url: args.registration_url,
        max_attendees: args.max_attendees,
        publishedAt: args.publishedAt || null
      }
    
      const response = await axios.post(
        `${this.strapiUrl}/content-manager/collection-types/api::event.event`,
        data,
        { headers }
      )
    
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(response.data, null, 2)
        }]
      }
    }
  • Defines the input schema for the strapi_create_event tool, specifying parameters, types, descriptions, and required fields.
    inputSchema: {
      type: 'object',
      properties: {
        title: { type: 'string', description: 'Event title' },
        description: { type: 'string', description: 'Event description in MARKDOWN' },
        event_type: { type: 'string', enum: ['webinar', 'workshop', 'meetup', 'conference'], description: 'Type of event' },
        start_date: { type: 'string', description: 'Event start date/time (ISO 8601)' },
        end_date: { type: 'string', description: 'Event end date/time (ISO 8601)' },
        location: { type: 'string', description: 'Physical location or virtual platform' },
        registration_url: { type: 'string', description: 'Registration/signup URL' },
        max_attendees: { type: 'number', description: 'Maximum number of attendees' },
        publishedAt: { type: 'string', description: 'Publication date (ISO 8601) or null for draft' }
      },
      required: ['title', 'description', 'event_type', 'start_date']
    }
  • index.js:278-295 (registration)
    Registers the strapi_create_event tool in the listTools response, including name, description, and input schema.
      name: 'strapi_create_event',
      description: 'Create a new event (webinar, workshop, meetup, conference)',
      inputSchema: {
        type: 'object',
        properties: {
          title: { type: 'string', description: 'Event title' },
          description: { type: 'string', description: 'Event description in MARKDOWN' },
          event_type: { type: 'string', enum: ['webinar', 'workshop', 'meetup', 'conference'], description: 'Type of event' },
          start_date: { type: 'string', description: 'Event start date/time (ISO 8601)' },
          end_date: { type: 'string', description: 'Event end date/time (ISO 8601)' },
          location: { type: 'string', description: 'Physical location or virtual platform' },
          registration_url: { type: 'string', description: 'Registration/signup URL' },
          max_attendees: { type: 'number', description: 'Maximum number of attendees' },
          publishedAt: { type: 'string', description: 'Publication date (ISO 8601) or null for draft' }
        },
        required: ['title', 'description', 'event_type', 'start_date']
      }
    },
  • index.js:406-407 (registration)
    Registers the handler dispatch in the CallToolRequestSchema switch statement, mapping the tool name to the createEvent method.
    case 'strapi_create_event':
      return await this.createEvent(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 full burden but lacks behavioral details. It doesn't disclose permissions needed, whether creation is idempotent, rate limits, or what happens on success/failure. 'Create' implies mutation, but no further context is given.

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 with no wasted words. It's front-loaded with the core action and includes helpful examples without redundancy.

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 insufficient. It doesn't explain return values, error conditions, or system behavior post-creation, leaving significant gaps for agent understanding.

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 parameters are well-documented in the schema. The description adds no parameter-specific information beyond the event_type examples, which are already in the enum. 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 verb ('Create') and resource ('a new event'), with examples of event types in parentheses. It distinguishes from siblings like strapi_create_blog_post by specifying the event domain, though it doesn't explicitly contrast with other creation tools.

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?

No guidance on when to use this tool versus alternatives is provided. The description doesn't mention sibling tools like strapi_publish_event for publishing or strapi_update_event for modifications, nor does it specify prerequisites or appropriate contexts for event creation.

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