weegloo-list-pagination

Paginate Weegloo list API responses using links.next and links.prev URLs.

1|2|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/weeglooapi/weegloo-mcp-plugin --skill weegloo-list-pagination-weeglooapi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: weegloo-list-pagination
Source: https://github.com/weeglooapi/weegloo-mcp-plugin/tree/main/plugins/weegloo/skills/weegloo-list-pagination
Command: npx skills add https://github.com/weeglooapi/weegloo-mcp-plugin --skill weegloo-list-pagination-weeglooapi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Weegloo list endpoints cap results at 100 items per page, so fetching complete datasets of medias, contents, or space-memberships requires correctly following the pagination links returned in each response instead of hand-building offset parameters. ## Core Features & Use Cases - Link-based pagination: Reads links.self, links.next, and links.prev from list responses and issues follow-up GET requests against the same API host. - First-page query construction: Guides setting limit (max 100, default 15), order, filters, and Media mimeGroups filters on the initial request. - Use Case: Building an infinite-scroll media library grid that loads images page by page by fetching links.next until it is absent, appending items each time. ## Quick Start Use the weegloo-list-pagination skill to fetch all image medias from my Weegloo space by following links.next through every page.

Frequently Asked Questions about weegloo-list-pagination

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I paginate Weegloo list API results?

Make the first list request with your limit, order, and filters, then read links.next from the JSON response and issue a GET to that path on the same API host. Repeat until links.next is absent, which indicates the last page.

What is the maximum limit for Weegloo list endpoints?

The limit parameter maxes out at 100 items per page, with a default of 15. Larger values are rejected by the API, so to retrieve more than 100 items you must page through links.next rather than raising the limit.

How do I filter Weegloo media lists by images or videos?

Add fields.file.{locale}.mimeGroups={MimeGroup} to the first-page medias query, for example mimeGroups=Image to restrict results to images. The filter is preserved automatically in subsequent links.next URLs.

Why does links.next disappear from my Weegloo API response?

links.next is omitted when there is no following page, meaning you have reached the end of the result set. Similarly, links.prev is omitted on the first page, so treat a missing links.next as the stop condition for iteration.

Can I build offset or skip parameters manually instead of using links?

The recommended approach is to treat links.next and links.prev as opaque strings and copy them onto the correct API origin. Hand-building pagination parameters risks inconsistency with the server-generated filters and ordering.