Skip to main content
Glama
GMPSignal MCP Server

GMPSignal MCP Server

fetch_actor_dataset_page

Read-onlyIdempotent

Retrieve paginated, sliced JSON items from a historical Apify Actor dataset by datasetId, or run a GMPSignal Actor slug with offset and limit controls.

Instructions

Paginate, slice, or retrieve structured JSON items from any historical Apify Actor run dataset by datasetId or execute any specific GMPSignal Actor slug with offset and limit pagination controls.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fetch_actor_dataset_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of dataset items to return in this page (1 to 250).
offsetNoZero-based item offset for dataset pagination.
actorSlugNoOptional GMPSignal Actor slug (e.g., "gmpsignal/dex-token-scanner-security-auditor") if fetching fresh paginated items.
datasetIdNoExisting Apify datasetId to paginate (if already executed), or leave empty to run actorSlug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.2

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is carried structurally. The description adds that results are structured JSON items paginated by offset/limit, but it omits what matters for the execute path — that running an actorSlug starts a run, may be slow, may consume credits, and is not the same operation as reading an existing dataset.

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

Conciseness3/5

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

It is a single sentence, front-loaded with the core action, but it is a run-on that stacks three near-synonyms ('Paginate, slice, or retrieve') and then restates 'offset and limit pagination controls' that the schema already defines. The dual-mode idea deserves its own clause or sentence rather than being tacked on with 'or'.

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?

With four optional parameters fully documented in the schema and no output schema, the description supplies enough for correct invocation: two modes, pagination model, and the item type returned. It leaves gaps around return envelope/termination and the synchronous nature of the execute path, but nothing blocking for a caller.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already explains limit (1-250, default 25), zero-based offset, datasetId length bounds and actorSlug. The description only reinforces the offset/limit pagination model and the datasetId-vs-actorSlug either/or, which is a marginal addition over the structured fields. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb stack (paginate/slice/retrieve) tied to a specific resource (Apify Actor run dataset, or GMPSignal Actor slug), and it names the two operating modes. The agent can tell this is a generic dataset-pagination utility rather than a domain query tool, though it never contrasts itself with the domain-specific siblings.

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

Usage Guidelines3/5

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

It does state a mode-selection rule: supply datasetId 'if already executed', otherwise leave it empty to run actorSlug. That is conditional guidance, but it is buried in the schema rather than the description and there is no when-not guidance or routing to the sibling tools that produce those datasets in the first place.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.