Skip to main content
Glama

Pagination Extraction

paginate

Extract data from multiple pages in one call. Handles click, scroll, and URL pagination with auto-detection of next buttons. Returns content and metadata from each page.

Instructions

Extract data across multiple pages in a single call. Handles click-next, infinite scroll, and URL-pattern pagination. Auto-detects 'next' buttons when nextSelector='auto'. Returns extracted content from each page plus metadata. Replaces 3-4 tool calls per page with one invocation. Cap: 50 pages, 100K total chars.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYesSession ID.
extractTypeNoWhat to extract from each page.text
extractTargetNoCSS selector to scope extraction to a specific container.
extractJsNoJavaScript expression for extractType='js'.
nextSelectorNoCSS selector for the next button, or 'auto' to detect automatically.auto
paginationTypeNoPagination strategy: click (next button), scroll (infinite scroll), url (URL pattern).click
urlPatternNoURL pattern with {page} placeholder for paginationType='url'.
maxPagesNoMaximum pages to extract. Default: 10.
delayMsNoDelay between pages in ms. Default: 1000.
maxCharsPerPageNoMax characters per page extraction. Default: 5000.
stopWhenNoStop condition. Default: auto (all heuristics).auto
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It mentions auto-detection, caps, and returns extracted content plus metadata, but lacks details on error handling, response structure, or rate limits.

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?

The description is concise with four sentences, front-loading the main purpose and key features. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (11 parameters, 3 enums, no output schema), the description explains the overarching functionality, caps, and efficiency gains. It lacks examples for URL patterns or stop conditions but is otherwise complete.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents all parameters. The description adds context for some parameters (nextSelector, paginationType) but does not significantly expand beyond the schema definitions.

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?

The description explicitly states that the tool extracts data across multiple pages, handling click-next, infinite scroll, and URL-pattern pagination. It differentiates from sibling tools like 'extract' by focusing on multi-page extraction and auto-detection of next buttons.

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

Usage Guidelines4/5

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

The description provides clear usage context, noting that the tool replaces 3-4 tool calls per page with one invocation. It specifies caps (50 pages, 100K total chars) but does not explicitly state when not to use or mention alternatives.

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/anthonybono21-cloud/leapfrog'

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