Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

OpenPanel: Export events csv

openpanel_export_events_csv
Read-only

Export events as CSV for spreadsheet analysis. Filter by site, date range, event type, and limit to generate data for reporting.

Instructions

[UNIFIED] Export events as CSV-formatted data for spreadsheet analysis. 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_csv"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
siteYes
eventNo
limitNo
startNo
project_idNo

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: the client must be in 'read' or 'root' mode. However, it says nothing about pagination, the default limit of 1000, date-range behavior, or the shape of the CSV output, which matter for a data-export call.

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?

Two compact sentences with the format and requirement front-loaded and no filler. The only waste is the '[UNIFIED]' tag, which conveys no actionable meaning to an agent.

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 6-parameter export tool with zero schema descriptions and no output schema, the definition is far too thin. The agent cannot determine filter semantics, date format, or what happens past the default limit, all of which are required to invoke it correctly.

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

Parameters1/5

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

Schema description coverage is 0% across 6 parameters, so the description carries the full burden of explaining them, and it explains none. Nothing is said about site, start, end, event, limit, or project_id, leaving the agent to guess at required scope, date format, and truncation behavior.

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?

States a specific verb and resource ('Export events') plus the output format ('CSV-formatted data'), which is the key differentiator from a generic events export. It does not explicitly name or contrast the sibling openpanel_export_events, and the '[UNIFIED]' prefix is unexplained noise, but the purpose is unambiguous.

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 phrase 'for spreadsheet analysis' implies a usage context, giving the agent a rough idea of when this format is preferred over a JSON export. There is no explicit when-not guidance, no mention of the sibling export tools, and no note about scope limits or prerequisites beyond the mode requirement.

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