zephyr-squad-server-mcp

export_cycle

Export test cycle executions to CSV and get a download link. Provide project, version, and cycle ID to generate the file.

Instructions

Get a download link for a cycle's executions as a CSV export.

project/version accept keys/names or ids (prefer ids when you have them, to skip a lookup; -1 = Unscheduled). Pass folder_id to export a single folder within the cycle (omit for the whole cycle). Returns {url: "…/Cycle-RC1.csv"} — a download link, not the file bytes; hand the URL to the user or fetch it separately.

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": {
      "cycle_id": "<cycle_id>",
      "project": "<project>",
      "version": "<version>"
    },
    "name": "export_cycle"
  }
}

Input Schema

Name	Required	Description	Default
`cycle_id`	Yes
`project`	Yes
`version`	Yes
`folder_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 24, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations provided, the description discloses that it returns a download link (not file bytes) and the response format. It adds details on parameter semantics. It could mention that it is a read-only operation, but overall transparency is good.

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

Conciseness5/5

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

The description is concise and well-structured. It leads with the main purpose, then provides parameter details and return value in a clear, scannable format. Every sentence adds value with no redundancy.

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?

Given 4 parameters, no output schema, and no annotations, the description covers the essential aspects: parameter flexibility, folder export option, and the nature of the return value. It could mention error handling or what the URL should be used for, but overall it is fairly complete for a straightforward export tool.

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 description coverage is 0%, but the description adds meaning: it explains that project/version accept various types and -1 for Unscheduled, and folder_id is optional for partial export. cycle_id is not elaborated, but the description compensates well for the lack of schema descriptions.

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 the tool's purpose: 'Get a download link for a cycle's executions as a CSV export.' It specifies the resource (cycle's executions) and action (download link), distinguishing it from sibling tools like get_cycle or list_executions.

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 usage context: it explains parameter types ('project/version accept keys/names or ids'), preference for ids, and the optional folder_id. It also clarifies what the tool returns. However, it does not explicitly state when not to use this tool or compare to alternatives.

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