Skip to main content
Glama
apify

actors-mcp-server

Official
by apify

Get dataset items

get-dataset-items
Read-onlyIdempotent

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

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
apifyConsoleUrlNoPersonalized Apify Console link to the dataset; present only for Console sessions
itemsYesDataset items
itemCountYesNumber of items returned
totalItemCountYesTotal items in dataset
offsetYesOffset used for pagination
limitYesLimit used for pagination
summaryYesSummary of the result
nextStepYesOne follow-up action with tool name
Behavior4/5

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

Beyond annotations (readOnlyHint, destructiveHint, idempotentHint), description adds defaults (limit 20), clean=true behavior, dot notation for nested fields, and pagination info in results. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with sections and examples. Each sentence adds information, but some redundancy (e.g., repeating dot notation explanation). Still highly focused given 8 parameters.

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?

Output schema is present (not shown). Description covers pagination, total count, and field selection behavior. Complete for a read operation with good annotations and schema coverage.

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 coverage is 100%, so baseline is 3. Description adds value by explaining defaults, dot notation shortcut, clean as composite, and flatten override. Provides examples for parameter usage.

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 the tool retrieves dataset items with pagination, sorting, and field selection. It uses specific verbs and contrasts with sibling tools like abort-actor-run, establishing its unique purpose.

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?

Includes a USAGE section with explicit scenarios ('Use when you need to read data from a dataset') and concrete examples. Lacks explicit when-not-to-use or alternatives, but context is clear.

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