Skip to main content
Glama
apify

actors-mcp-server

Official
by apify

Get dataset items

get-dataset-items
Read-onlyIdempotent

Fetch paginated items from a dataset, selecting only needed fields using dot notation. Optionally sort, filter empty items, and exclude hidden fields.

Instructions

Retrieve dataset items with pagination, sorting, and field selection. Items can be large; when you only need specific columns, pass fields to reduce response size (use get-dataset first if you don't know the field names). 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
descNoIf true, results are returned in reverse order (newest to oldest).
omitNoComma-separated list of fields to exclude from results.
cleanNoIf true, returns only non-empty items and skips hidden fields (starting with #). Shortcut for skipHidden=true and skipEmpty=true.
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.
offsetNoNumber of items to skip at the start. Default is 0.
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.
datasetIdYesDataset ID or username~dataset-name.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesDataset items
limitYesLimit used for pagination
offsetYesOffset used for pagination
summaryYesSummary of the result
nextStepYesOne follow-up action with tool name
datasetIdYesDataset ID
itemCountYesNumber of items returned
totalItemCountYesTotal items in dataset
apifyConsoleUrlNoPersonalized Apify Console link to the dataset; present only for Console sessions
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. Description adds operational details beyond annotations: default limit=20, field selection via dot notation, clean=true behavior, and auto-flattening. 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?

Description is front-loaded with purpose, then details, then usage. Efficiently uses bullet points and examples. A minor improvement could be further condensing but overall well-structured and clear.

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 output schema exists, description doesn't need to detail return values but still mentions pagination info and total count. With 8 parameters and 1 required, it adequately covers necessary context without omissions.

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% with descriptions. The description adds valuable usage context (e.g., why to use 'fields', how to specify nested fields, diagnostic override for 'flatten') that goes beyond schema text.

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 retrieves dataset items with pagination, sorting, and field selection, using specific verbs and resource. It distinguishes from sibling tools (none are dataset-item operations).

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?

Provides explicit usage guidance ('Use when you need to read data from a dataset') and two concrete examples. Could mention when not to use, but no close siblings exist, so ambiguity is low.

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