Skip to main content
Glama

Export board / history / optimizer / audit

export_data
Idempotent

Export a project's board, rank history, optimizer drafts, or audit as CSV/JSON, or write them to the exports folder; use fastlane to generate a zip of deliver/supply metadata.

Instructions

Export a project's board, rank history, optimizer drafts or audit as CSV or JSON. By default returns the content (cut at maxChars); with saveToFile:true writes the file into the app's exports folder instead. format fastlane (what optimizer only) always writes a zip of fastlane deliver / supply metadata to the exports folder.

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": {
      "projectId": "<projectId>",
      "what": "<what>",
      "format": "<format>"
    },
    "name": "export_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
whatYesWhat to export.
formatYesFile format.
maxCharsNoMax characters of content to return (default 50000).
projectIdYesProject id (from get_overview).
saveToFileNoWrite to <dataDir>/exports instead of returning content.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.0
    • changedInput schema / properties / what / enum
      Previous value: -[
      -  "board",
      -  "history",
      -  "optimizer"
      -]New value: +[
      +  "board",
      +  "history",
      +  "optimizer",
      +  "audit"
      +]
  2. First observedv0.1.7

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, idempotentHint=true and destructiveHint=false; the description goes further by disclosing that content may be truncated ('cut at maxChars') and that file writing occurs into the app's exports folder, which explains why the tool is not read-only. The most valuable disclosure is the format-specific exception: fastlane 'always writes a zip' regardless of saveToFile, a side effect the annotations cannot express. It stops short of saying what path is returned or what happens to pre-existing files of the same name.

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 sentences, front-loaded with the resource list followed by delivery behavior, and every clause carries information (default behavior, truncation, folder target, format exception). The parenthetical 'format fastlane (what optimizer only)' is slightly compressed/awkward phrasing that costs a bit of readability.

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

Completeness5/5

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

With five parameters, no output schema, and two enums, the description covers the decisions an agent actually has to make: which resource, which format, whether to return or persist, and the truncation ceiling. The only residual gap (returned file path on save) is minor for a tool of this complexity.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3, but the description adds a real constraint absent from the schema: fastlane is only meaningful with what=optimizer and it produces a zip of deliver/supply metadata. That maps cross-parameter validity and output shape onto the enum values, which the bare schema does not convey.

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 opens with a specific verb plus an enumerated resource set ('board, rank history, optimizer drafts or audit') and the output formats, so an agent can immediately tell it apart from read-side siblings such as get_project_board, get_audit, or screenshots_export.

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?

It clearly contrasts the two delivery modes (return content by default vs. saveToFile:true), which is effectively usage guidance for the delivery decision. However, it never states when to pick this tool over the sibling readers that surface the same data (get_project_board, get_audit), nor does it note prerequisites, leaving that selection to inference.

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