analyze_ingestion_file
Parse WP export files (JSON/CSV/XML) or import live from WordPress REST API
Overview
The first step in any WordPress cloning project. This tool reads your WordPress or WooCommerce export file and understands its structure — every field, every custom attribute, every serialized PHP blob. It can also import directly from a live WordPress site via the REST API. It tells you exactly what data you're working with so nothing gets lost in translation. Note: local filesystem paths are not accessible to remote MCP callers — the MCP server runs in a separate container.
How It Works
- Provide a source_url (HTTPS download link for the export file) or wordpress_url (live WordPress site for REST API import). filePath is reserved for in-process use only and is not supported by remote MCP callers.
- The tool detects the file type and parses it, handling WordPress-specific quirks like PHP-serialized meta fields.
- It analyzes up to 50 rows to detect all fields, custom attributes, and data patterns.
- Returns a structured analysis with field names, sample data, custom attributes, and cloning recommendations.
Input Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
source_url |
string |
optional | HTTPS URL to download the export file from. Max 100MB. This is the standard option for remote MCP callers. |
wordpress_url |
string |
optional | URL of a live WordPress site to import content from via REST API (e.g. https://example.com) |
wc_consumer_key |
string |
optional | WooCommerce consumer key for authenticated API access. Required with wc_consumer_secret to pull WooCommerce data. |
wc_consumer_secret |
string |
optional | WooCommerce consumer secret. Required when wc_consumer_key is provided. |
filePath |
string |
optional | [Not supported for remote MCP callers] Reserved for in-process use only. Remote callers must use source_url or wordpress_url instead. |
fileType |
json | xml | csv |
optional | Format of the export file (required for source_url/filePath; auto-set to json for wordpress_url) |
maxRows |
number |
optional | Maximum rows to analyze (default: 50, max: 500) |
job_id |
string |
optional | Optional clone job ID. When provided, persists analysis to database_mapping_source_file and uploads the file to B2. |
What You Get Back
- Total record count
- List of all detected fields (columns/keys)
- Custom attributes found in meta data
- Sample data rows for verification
- Recommendations for schema design
Example Use Case
You have a WooCommerce product export CSV with 2,000 products hosted at a public URL. Pass source_url to download and analyze it — the tool discovers all custom fields (like _sale_price, _stock_status, custom taxonomies) so your new schema captures everything.