Skip to main content
Glama
rapid7

Rapid7 Bulk Export MCP Server

Official
by rapid7

Start Rapid7 Export

start_rapid7_export
Idempotent

Initiates a non-blocking Rapid7 bulk export (vulnerability, policy, or remediation), returning an export ID. Automatically splits remediation exports exceeding 31 days into multiple chunks.

Instructions

Start a new Rapid7 export job (non-blocking).

This is a fast, non-blocking call that creates an export job on the Rapid7 platform and returns the export ID immediately. The export will process in the background on Rapid7's servers (typically 3-5 minutes).

Use check_rapid7_export_status(export_id) to monitor progress, then download_rapid7_export(export_id, export_type="...") once it completes.

If an export from today already exists, returns that export's ID instead of creating a duplicate.

For remediation exports, the Rapid7 API limits each request to 31 days. If the date range exceeds 31 days, this tool automatically splits it into multiple 31-day chunks and kicks off an export for each chunk.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_dateNoEnd date in YYYY-MM-DD format (only for remediation exports). Defaults to today if not specified.
start_dateNoStart date in YYYY-MM-DD format (only for remediation exports). Defaults to 30 days ago if not specified.
export_typeNoType of export to create. One of "vulnerability", "policy", or "remediation".vulnerability

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations indicate idempotentHint=true, and description explains that existing exports are reused. It also discloses non-blocking nature, background processing time (3-5 minutes), and automatic date range splitting. No contradictions; adds context beyond annotations.

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?

Well-structured with clear paragraphs and bullet points. Each sentence adds value, no fluff. Information is front-loaded and logically organized.

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?

Given output schema exists and schema coverage is 100%, the description provides complete behavioral guidance: initiation, monitoring, download, deduplication, and date handling. No gaps for an agent to invoke correctly.

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

Parameters5/5

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

Schema covers all 3 parameters with descriptions. Description adds crucial context: export_type specifies the type, start_date/end_date are only for remediation, with default behavior (30 days ago to today) and automatic 31-day chunking. Schema coverage is 100%, but description provides additional semantic value.

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?

Description explicitly states the tool starts a Rapid7 export job (non-blocking), specifies export types, and automatically splits long date ranges for remediation exports. It clearly distinguishes from sibling tools like check_rapid7_export_status and download_rapid7_export.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear when-to-use (to initiate an export) and what to do after (monitor with check_rapid7_export_status, download with download_rapid7_export). Explains duplicate detection (returns existing ID if today's export exists) and the 31-day chunking behavior for remediation exports.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rapid7/rapid7-bulk-export-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server