TinyRex MCP

list_actors

Discover which public TinyRex Apify Store actors this MCP can run. Returns each actor's name, title, short description, Store URL, and example input; private or blocked actors are excluded.

Instructions

List all public TinyRex Apify Store actors this MCP can run.

Returns name, title, short description, Store URL, and an example input for each actor. Private / ToS-blocked actors are not included.

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": "list_actors"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 16, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations are provided, so the description carries the burden. The 'List' verb signals a read-only, side-effect-free operation, and it proactively discloses filtering behavior by naming what is excluded (private and ToS-blocked actors) -- a genuinely useful behavioral trait. It does not address auth requirements, result size, or pagination, which keeps it short of a 5.

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?

Three short sentences, front-loaded with the core action, followed by the return shape and then the exclusion caveat. No sentence is wasted and the most important information comes first.

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?

For a zero-parameter discovery tool, the description covers what is returned and what is deliberately omitted, and an output schema exists to carry the exact return structure. Nothing an agent needs in order to call it correctly is missing.

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?

The tool takes zero parameters, which is the baseline-4 case. There is nothing for the description to clarify beyond confirming the call is argument-free, and the schema reflects that.

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?

States a specific verb and resource ('List all public TinyRex Apify Store actors') with scope qualifiers that tie it to run_actor's capability set ('this MCP can run'). An agent immediately understands this is the enumeration/discovery tool, clearly distinct from run_actor.

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?

Usage is implied rather than stated: it enumerates exactly the actors run_actor can execute, but the description never says 'call this first to discover valid inputs for run_actor' or notes any preconditions. The exclusion clause ('Private / ToS-blocked actors are not included') is helpful context but is not routing guidance.

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

Deploy Server