Skip to main content
Glama

OpenPanel: Export events

openpanel_export_events
Read-only

Export raw event records by site, date range, event, profile, or project with pagination filters. Returns individual events for analysis or reporting.

Instructions

[UNIFIED] Export raw event data with filters and pagination. Returns individual event records. Requires 'read' or 'root' mode client.

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": {
      "site": "<site>"
    },
    "name": "openpanel_export_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
pageNo
siteYes
eventNo
limitNo
startNo
includesNo
profile_idNo
project_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0
  2. Removedv3.13.1
  3. First observedv3.4.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description does not contradict that. It adds genuinely useful behavior beyond the annotations: results are individual event records (not aggregates), the tool is paginated, and it requires a 'read' or 'root' mode client — an auth prerequisite the schema does not express.

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?

Three short sentences, with the core purpose front-loaded ahead of the return-shape note and the auth requirement. The "[UNIFIED]" tag adds no information and is the only real waste.

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 nine-parameter read/export tool with zero schema description coverage and no output schema, the description is too thin. It never explains what the filters accept or in what format dates and identifiers are expected, leaving an agent to guess on nearly every argument.

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

Parameters2/5

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

Schema description coverage is 0% across nine parameters, so the description must carry the burden and it does not. Only a vague reference to "filters and pagination" appears; there is no explanation of site, event, start/end formats, includes, profile_id, project_id, limit, or page semantics.

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?

"Export raw event data" gives a specific verb and resource, and "Returns individual event records" clarifies the granularity of what comes back. However, the "[UNIFIED]" prefix is opaque, and the description never distinguishes this tool from the sibling openpanel_export_events_csv, which an agent would plausibly confuse it with.

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: "export raw event data" suggests bulk/raw retrieval as opposed to the aggregated report tools, but no explicit when-to-use or when-not-to-use condition is stated. The prerequisite "Requires 'read' or 'root' mode client" is the one concrete gating instruction provided.

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

Deploy Server

Other Tools