Skip to main content
Glama
the-events-calendar

The Events Calendar MCP Server

Official

tec-calendar-read-entities

Read, list, or search events, venues, organizers, and tickets with filters like date range, location, status, and price.

Instructions

Read, list, or search calendar posts.

Use Cases

  1. Get single post: provide postType and id

  2. List all posts: provide postType only

  3. Search posts: provide postType and query

Query Capabilities

  • Get single post by ID

  • List all posts with pagination

  • Search posts by keyword

  • Filter by post-specific criteria

  • Combine multiple filters

Examples

Basic Queries

1. Get specific event by ID

{ "postType": "event", "id": 123 }

2. List all venues with pagination

{ "postType": "venue", "per_page": 20, "page": 1 }

3. Search events by keyword

{ "postType": "event", "search": "conference" }

4. Get all organizers sorted by name

{ "postType": "organizer", "orderby": "title", "order": "asc" }

Date Filtering

5. Get upcoming events

{
  "postType": "event",
  "eventFilters": {
    "start_date": "2024-12-06"
  }
}

6. Get events in date range

{
  "postType": "event",
  "eventFilters": {
    "start_date": "2024-12-01",
    "end_date": "2024-12-31"
  }
}

Location Filtering

7. Find venues by city and state

{
  "postType": "venue",
  "venueFilters": {
    "city": "San Francisco",
    "state": "CA"
  }
}

8. Find venues near coordinates

{
  "postType": "venue",
  "venueFilters": {
    "geo_lat": 37.7749,
    "geo_lng": -122.4194,
    "radius": 10
  }
}

Relationship Queries

9. Get events at specific venue

{ "postType": "event", "eventFilters": { "venue": 456 } }

10. Get tickets for specific event

{ "postType": "ticket", "ticketFilters": { "event": 123 } }

11. Get available tickets only

{
  "postType": "ticket",
  "ticketFilters": {
    "event": 123,
    "available": true
  }
}

Status & Filtering

12. Get only published events

{ "postType": "event", "status": "publish" }

13. Get draft and pending venues

{ "postType": "venue", "status": ["draft", "pending"] }

Complex Queries

14. Search published events at venues with dates

{
  "postType": "event",
  "search": "workshop",
  "status": "publish",
  "eventFilters": {
    "venue": 456,
    "start_date": "2024-12-01"
  },
  "per_page": 50
}

15. Get tickets under $50 sorted by price

{
  "postType": "ticket",
  "ticketFilters": {
    "max_price": 50,
    "available": true
  },
  "orderby": "price",
  "order": "asc"
}

Available Filters

  • eventFilters: venue, organizer, featured, categories, tags

  • venueFilters: city, state, country, zip, geo_lat/lng, radius

  • ticketFilters: event, type, provider, min/max_price

  • organizerFilters: email, website, phone

  • Common: status, search, include, exclude, page, per_page, orderby

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
postTypeYesThe type of post to read
idNoPost ID for single post retrieval
queryNoSearch query string
pageNoPage number
per_pageNoItems per page
orderNoSort order
orderbyNoField to order by
statusNoPost status filter
includeNoInclude specific IDs
excludeNoExclude specific IDs
eventFiltersNoEvent-specific filters (only used when postType is "event")
venueFiltersNoVenue-specific filters (only used when postType is "venue")
organizerFiltersNoOrganizer-specific filters (only used when postType is "organizer")
ticketFiltersNoTicket-specific filters (only used when postType is "ticket")
Behavior3/5

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

No annotations are provided, so the description must convey behavioral traits. It implies read-only behavior through examples and the tool name, but it does not explicitly state that this tool does not modify data, require specific permissions, or have rate limits. The examples are thorough but lack a clear safety statement.

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

Conciseness4/5

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

The description is well-structured with a clear hierarchy: purpose, use cases, examples, and filter summary. It is front-loaded with essential information. However, it is lengthy due to 15 examples; some could be condensed without losing clarity. Overall, it balances detail and organization well.

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 (14 parameters, nested objects, no output schema), the description covers parameter usage comprehensively but is incomplete regarding return values, pagination behavior, and error handling. With no output schema, the agent would benefit from knowing what the response contains.

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

Parameters5/5

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

Schema coverage is 100%, yet the description adds significant value by grouping parameters into use cases, providing 15 detailed examples showing valid combinations, and explaining conditional filters (e.g., eventFilters only for events). This greatly enhances parameter understanding beyond the schema.

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

Purpose5/5

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

The description clearly states 'Read, list, or search calendar posts' and immediately outlines three use cases (get single, list all, search). The tool name 'tec-calendar-read-entities' combined with sibling tools for create-update and delete effectively distinguishes its purpose as read-only.

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

Usage Guidelines4/5

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

The description provides clear use cases and example queries that guide when to use each mode (single vs list vs search). However, it does not explicitly state when not to use this tool (e.g., for modifications) or reference sibling tools. The context from sibling names helps, but an explicit exclusion would improve clarity.

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/the-events-calendar/mcp-server'

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