Arguments passed to the connector tool. String values support {placeholders}. In 'perJob' mode: {title}, {company}, {location}, {url}, {source}, {jobType}, {remote}, {salary}, {description}, {postedDate}, {tags}, {keyword}, {jobCount}, and {message}. In 'summary'/'chunked' mode: {jobsText} (formatted job list, or one part of it in chunked mode), {keyword}, {jobCount}, and in chunked mode also {part}/{partCount}. IMPORTANT: this must match the tool's real argument shape exactly, or every call fails with an MCP 'Input validation error' (the dataset is unaffected - only delivery is skipped). After your first run, check the run log for 'Tool ... expects arguments shaped like:' followed by the connector's own full JSON Schema for the selected tool. For Notion's official 'notion-create-pages' tool (confirmed from its schema): the call takes a top-level "pages" ARRAY (max 100, required) plus an optional top-level "parent" object - {"page_id": "..."}, {"database_id": "..."}, or {"data_source_id": "..."} (omit entirely to create private workspace-level pages). Each item inside "pages" only accepts "properties" (a flat map of property name to string/number/array-of-strings/null - not the raw Notion API's nested rich_text format), "content" (Markdown), "template_id", "icon", and "cover" - a "parent" key inside a page item is rejected. Example (perJob mode, one call per job, creating a database page each time): {"parent": {"database_id": "YOUR_NOTION_DATABASE_ID"}, "pages": [{"properties": {"Name": "{title}", "Company": "{company}", "Location": "{location}", "URL": "{url}", "Source": "{source}"}, "content": "{description}"}]}. Match the property names to your actual Notion database's columns.