Skip to main content
Glama
apify

actors-mcp-server

Official
by apify

get-dataset-items

Read-onlyIdempotent

Retrieve dataset items with pagination, sorting, and field selection. Use dot notation for nested fields and skip empty items with clean=true.

Instructions

Retrieve dataset items with pagination, sorting, and field selection. For nested fields use dot notation (e.g., fields="metadata.url") — the server auto-flattens parent prefixes. Defaults limit to 20. Use clean=true to skip empty items and hidden fields.

The results will include items along with pagination info (limit, offset) and total count.

USAGE:

  • Use when you need to read data from a dataset (all items or only selected fields).

USAGE EXAMPLES:

  • user_input: Get first 20 items from dataset abd123

  • user_input: Get only metadata.url and title from dataset username~my-dataset

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
datasetIdYesDataset ID or username~dataset-name.
cleanNoIf true, returns only non-empty items and skips hidden fields (starting with #). Shortcut for skipHidden=true and skipEmpty=true.
offsetNoNumber of items to skip at the start. Default is 0.
limitNoMaximum number of items to return. Defaults to 20.
fieldsNoComma-separated list of fields to include in results. Fields in output are sorted as specified. Use dot notation for nested objects (e.g. "metadata.url"); the server auto-flattens parent prefixes.
omitNoComma-separated list of fields to exclude from results.
descNoIf true, results are returned in reverse order (newest to oldest).
flattenNoComma-separated list of fields to flatten (e.g. flatten="metadata" turns {"metadata":{"url":"x"}} into {"metadata.url":"x"}). Normally derived automatically from dot-notation in `fields`; specify only as a diagnostic override.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
datasetIdYesDataset ID
itemsYesDataset items
itemCountYesNumber of items returned
totalItemCountNoTotal items in dataset
offsetNoOffset used for pagination
limitNoLimit used for pagination
Behavior5/5

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

Annotations declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds significant behavioral context beyond annotations: default limit of 20, clean parameter behavior, dot notation for nested fields, flatten parameter as diagnostic override, and pagination info in results. No contradictions with annotations.

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 well-structured: a concise main sentence, followed by key details (dot notation, defaults, clean), then USAGE and examples. Every sentence adds value without redundancy. It is front-loaded and easy to parse.

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

Completeness5/5

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

Given the 8 parameters (most optional), annotations present, and an existing output schema (context signal says true), the description covers all essential aspects: pagination defaults, field selection, cleanup, and usage context. It is complete for an agent to correctly select and invoke the tool.

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

Parameters4/5

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

Schema has 100% coverage with descriptions for all 8 parameters. The description adds value by explaining dot notation auto-flattening, clarifying clean as a shortcut for skipHidden and skipEmpty, and noting default limit. This enhances understanding beyond the schema alone.

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 'Retrieve dataset items with pagination, sorting, and field selection,' specifying the action (retrieve), resource (dataset items), and key features. It distinguishes this tool from sibling tools like 'call-actor' or 'fetch-actor-details' which serve different purposes.

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 includes a USAGE line: 'Use when you need to read data from a dataset (all items or only selected fields),' providing clear context. It also includes usage examples. However, it does not explicitly state when not to use this tool or mention alternatives like 'get-key-value-store-record' for comparison.

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/apify/apify-mcp-server'

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