Skip to main content
Glama
Sign In

Tulina

by ai.tulina.mcp
OverviewDiscussionsAdmin

apify_actor

Read-only

Fetch one actor's card: builds, versions and defaultRunOptions (default memory and timeout).

Read it before a first run to size memory_mbytes/timeout_secs. The actor's INPUT fields are documented on its Store page, not here.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "actor_id": "<actor_id>"
    },
    "name": "apify_actor"
  }
}

Input Schema

NameRequiredDescriptionDefault
_orgNoOrg (id) de CET APPEL. `oto_list_orgs()`.
_groupNoÉquipe (id) de CET APPEL, sous son org parente.
_run_idNoOBLIGATOIRE à chaque appel dès `run_start` ou `data_claim_next` : sans lui, l'écriture sur une ligne réservée est refusée. Hérité seulement si le serveur tient un run actif — n'y compte pas.
_projectNoProjet (id) de CET APPEL — jeton PRIMAIRE. `oto_project(op='list')`.
actor_idYes`username/actor-name` (as shown in the Store) or its id.
_instanceNoInstance de connecteur PRÉCISE (un credential exact). `oto_instance(op='list')`.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description earns credit for disclosing what the card actually contains (builds, versions, defaultRunOptions with default memory and timeout) and, importantly, what it does NOT contain (input schema). It says nothing about freshness, error behavior for unknown actor ids, or rate limits.

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?

Three tight sentences, front-loaded with what is returned, then when to read it, then the scope exclusion. No filler; only the awkward line wrapping keeps it from being maximal.

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?

A read-only single-parameter lookup with no output schema, and the description covers both the return payload and the deliberate omission of input fields. An agent has enough to decide to call it; only the precise shape of defaultRunOptions is left implicit.

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 documents actor_id as 'username/actor-name or its id', and the description adds no syntax detail beyond that. The memory_mbytes/timeout_secs mentions refer to parameters of a different (run) tool, so they do not deepen this tool's parameter semantics.

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?

A specific verb ('Fetch') plus a specific resource ('one actor's card') plus the exact payload ('builds, versions and defaultRunOptions'). The singular 'one actor's card' implicitly separates it from the plural apify_actors sibling, but no sibling is named explicitly.

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?

Gives concrete timing guidance ('Read it before a first run to size memory_mbytes/timeout_secs') and draws a scope boundary by saying the actor's INPUT fields live on the Store page, not here. It stops short of naming which sibling to call instead for listing actors.

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

All Tulina toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources