Skip to main content
Glama
YawLabs

@yawlabs/aws-mcp

Official
by YawLabs

aws_paginate

Read-onlyIdempotent

Fetch paginated AWS list or describe results with configurable page size and resume token. Handles JMESPath queries without breaking pagination, preventing output limit issues.

Instructions

Fetch one page of a paginated AWS list/describe operation. Identical to aws_call plus maxItems (page size) and startingToken (resume cursor). When query is supplied it is wrapped server-side as {NextToken, items: } so pagination survives a projection that would otherwise drop NextToken; the handler unwraps items before returning. Returns the parsed response, a nextToken (null when the list is exhausted), and hasMore. Call again with the returned nextToken as startingToken until hasMore is false. Use this instead of aws_call for operations that might exceed the 5 MB stdout cap: list-objects-v2, describe-instances, describe-log-streams, list-roles, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serviceYesAWS service in kebab-case: 's3api', 'ec2', 'iam', 'logs', etc.
operationYesPaginated operation: 'list-objects-v2', 'describe-instances', 'list-roles', etc.
paramsNoOperation parameters (PascalCase keys) passed via --cli-input-json.
queryNoJMESPath expression to extract fields from each page (--query). The query is wrapped server-side as {NextToken, items: <query>} so pagination still works even when the projection drops NextToken; the handler unwraps `items` before returning.
maxItemsNoItems per page (1-10000). Default 100. Lower this if hitting the 5 MB output cap.
startingTokenNoResume cursor from the previous call's `nextToken`. Omit for the first page.
profileNoOverride session profile for this call.
regionNoOverride session region for this call.
timeoutMsNoTimeout in milliseconds. Default 60000.
Behavior5/5

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

The description explains the query wrapping mechanism, the return fields (parsed response, nextToken, hasMore), and pagination continuation. Annotations already declare readOnly=true, but the description adds valuable behavioral context beyond that.

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 a single focused paragraph, front-loading the purpose, then detailing mechanics and usage. Every sentence adds value with no 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?

The description covers the essential behavioral aspects and pagination loop. Without an output schema, it explicitly mentions return fields. It lacks mention of error handling or edge cases, but overall it is sufficiently complete for an experienced AWS user.

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

Parameters5/5

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

Schema coverage is 100%, and the description enriches parameters by explaining defaults (maxItems=100), the effect of query wrapping, and the role of startingToken. It also clarifies how params are passed via --cli-input-json.

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 clearly states it fetches one page of a paginated AWS list/describe operation and distinguishes from aws_call by adding maxItems and startingToken. It identifies specific usage scenarios like avoiding the 5 MB cap.

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

Usage Guidelines5/5

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

The description explicitly says to use this instead of aws_call for operations that might exceed the 5 MB cap, listing examples. It implies aws_call for non-paginated operations, providing clear when-to-use guidance.

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/YawLabs/aws-mcp'

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