Octoparse data collection

The Octoparse platform's collection capability, exposed for an agent to drive through the MCP server.

Collection reaches the user through more than one path, and Step 1 picks between them. Preset templates are the largest today; the tasks the user built themselves are already on the account and cost nothing to look up; managed datasets beat templates where they overlap; agent-generated tasks are planned for the long tail. Route to the capability that fits the request, not to templates by default.

Division of responsibility — read this before anything else:

• This skill routes. Which capability applies, which template fits within it, which pairs are real chains, what to avoid.
• The MCP service executes and holds truth about schemas. Input/output fields, sourceTree, pricing, and current availability come from search_templates at run time, never from memory.
• data/catalog.json is a routing projection only — it is regenerated from upstream, carries no input or output schemas, and is read by this repository's checks rather than by you at run time.

Never assemble parameters from this skill's prose or from a remembered field name. Always read the live inputSchema first.

Prerequisites

Octoparse MCP server connected and authorized. If search_templates fails with an auth error, use the octoparse-mcp-setup skill.

Workflow