Skip to main content

​
Fetching web content

Atomic’s bundled fetch_content tool reads webpages, PDFs, GitHub repositories, YouTube videos, and local video files.

​
Arguments

Always pass the lowercase urls field as a nonempty array of strings, even for one URL:
For multiple pages:
For a video, include the question in prompt:
Existing prompts or integrations using {"url": "..."} must change to {"urls": ["..."]}. The singular url field is no longer accepted by fetch_content. This does not change the url selector on get_search_content. Atomic can normalize a scalar urls string into a one-item array. Always use the documented array form in prompts and integrations; the legacy url field is not normalized.

​
Troubleshooting

If argument validation fails, check that:
  • The field is urls, not URLs or url.
  • Its value is an array, not a string or an object.
  • The array contains at least one nonempty string.
  • The call has no unrecognized fields.
When fetched content is truncated, follow the returned get_search_content call to retrieve the stored content.