Crawlora MCP

Official

by Crawlora-org

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

luma_place_events

List and search public events for a Luma place, with optional query and cursor-based pagination to browse event feeds.

Instructions

List and search public events for a Luma place. Returns public event cards for a Luma place. The optional query, page limit, and cursor mirror the place's public event feed. Follow the returned next_cursor only when has_more is true.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "place_slug": "<place_slug>"
    },
    "name": "luma_place_events"
  }
}

Input Schema

Name	Required	Description
`query`	No	Luma event search text
`place_slug`	Yes	Luma place page slug
`pagination_limit`	No	Page size; Luma returns at most 50 entries
`pagination_cursor`	No	Opaque cursor returned by Luma

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose useful behavior beyond the schema: results are limited to public events, returned as event cards, and next_cursor should only be followed when has_more is true. It omits auth requirements, result ordering, and whether pagination can be exhausted within the 50-entry page cap.

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

Conciseness3/5

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

The definition is short and front-loaded, but the second sentence ('Returns public event cards for a Luma place') largely restates the first and repeats 'for a Luma place'. One sentence of redundancy weakens otherwise efficient phrasing.

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

Completeness4/5

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

With four simple parameters, no annotations, and no output schema, the description covers the essentials an agent needs: input intent, result type, and the pagination contract. Missing only acquisition of the required slug and any mention of authorization or ordering, which are minor for this complexity.

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 coverage is 100%, so the baseline is 3. The description adds only marginal meaning, tying query, page limit, and cursor to the place's public event feed and clarifying the has_more/next_cursor relationship, which the schema does not state.

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 states a specific verb and resource ('List and search public events for a Luma place'), which clearly separates it from sibling event tools such as luma_calendar_events or luma_category_events by scoping results to a place. It does not explicitly name those siblings, so it stops short of a 5.

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?

Usage is only implied: the agent can infer this tool is for place-scoped public event browsing, and the pagination sentence implies an iterative call pattern. There is no explicit statement of when to prefer this over a calendar or category event listing, and no note that place_slug must be obtained first (e.g., via luma_place).

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

Deploy Server