Meta Ad Library, Google Ads Transparency & Video Ad Analyzer

Fetch Actor details

fetch-actor-details

Read-onlyIdempotent

Get detailed information about an Actor by its ID or full name (format: "username/name", e.g., "apify/rag-web-browser").

Requires the exact ID or full name — do not construct a plausible-looking name and call this tool with it.

Use 'output' to control returned information:

Default: all fields except outputSchema and serverInterface.
Selective: set only the fields you need to true, e.g. output: { inputSchema: true }
Common patterns: inputSchema only, description + readme, serverInterface: true (full API schema when it fits, operation navigation otherwise), "GET /search" (operation excerpt), or "#/components/schemas/Name" (referenced schema node) for Server Actors

The 'readme' field returns the summary when available, full README otherwise. Use when querying Actor details, documentation, or input requirements.

EXAMPLES:

What does apify/web-fetch do?
What is the input schema for apify/web-scraper?
What HTTP operations does this Server Actor expose?

Input Schema

Name	Required	Description	Default
`actor`	Yes	Actor ID or full name in the format "username/name", e.g., "apify/rag-web-browser".
`output`	No	Specify which information to include in the response to save tokens.

Output Schema

Name	Required	Description
`readme`	No	Actor README summary when available, otherwise the full README documentation.
`actorInfo`	No
`inputSchema`	No	Actor input schema.
`outputSchema`	No	Output schema inferred from successful runs.
`serverInterface`	No	The Actor's server interface. `output.serverInterface: true` returns the full API schema with guidance when it fits, or operation navigation otherwise. A "METHOD /path" string returns an operation excerpt; "#/..." returns a raw local schema node.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 29, 2026

removedInput schema / properties / output / properties / mcpTools

Removed value: -{
-  "description": "List available tools (only for MCP server Actors).",
-  "type": "boolean"
-}

removedOutput schema / properties / mcpTools

Removed value: -{
-  "description": "Markdown listing of MCP tools exposed by the Actor (only present when `output.mcpTools` is requested).",
-  "type": "string"
-}

Changed3 schema fields changedOct 27, 2026

addedInput schema / properties / output / properties / serverInterface

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "string"
+    }
+  ],
+  "description": "Server Actor HTTP API. true: full schema with guidance when it fits; otherwise operation navigation.\n\"METHOD /path\" (e.g. \"GET /search\"): operation excerpt. \"#/...\": raw node at a local JSON pointer.\nEach section is limited to 262144 UTF-8 bytes including guidance. References are not expanded or fetched."
+}

removedOutput schema / properties / actorInfo / properties / stats / properties / bookmarks
```
Removed value: -{
-  "description": "Number of bookmarks",
-  "type": "number"
-}
```

addedOutput schema / properties / serverInterface

Added value: +{
+  "description": "The Actor's server interface. `output.serverInterface: true` returns the full API schema with guidance when it fits, or operation navigation otherwise. A \"METHOD /path\" string returns an operation excerpt; \"#/...\" returns a raw local schema node.",
+  "type": "string"
+}

First observedOct 18, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world, so the safety profile is handled. The description still adds useful behavior: the default field set (all except outputSchema and serverInterface), the token-saving selective pattern, the readme fallback (summary when available, full README otherwise), and the 262144-byte section limit with un-expanded references.

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?

Front-loaded with the core action and the exact-name constraint, then segmented by purpose (output control, readme, when to use, examples). Slightly long, and the readme sentence partly duplicates the schema property text, but the density of routing information justifies most of the length.

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 an output schema present, return values need no explanation, and annotations cover safety; the description fills the remaining gap by explaining default vs selective field sets and Server Actor interface modes. It is silent on failure behavior (e.g., an actor that does not exist) and on how to obtain a valid ID, which would complete the picture.

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 the baseline is 3. The description goes beyond it by explaining how to combine the `output` flags in practice (selective true-flags, "common patterns" list, serverInterface string forms) and by clarifying the readme fallback semantics rather than just restating the field names.

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 ("Get detailed information about an Actor") plus the exact lookup key (ID or "username/name"), with a concrete example. Siblings operate on entirely different entities (runs, datasets, key-value stores, video analyses), so the resource distinction is unambiguous.

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?

Explicitly says "Use when querying Actor details, documentation, or input requirements" and backs that with four representative example questions. It adds a hard constraint ("Requires the exact ID or full name — do not construct a plausible-looking name"), but never names an alternative tool for discovering an ID, which is the natural when-not case.

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

All Meta Ad Library, Google Ads Transparency & Video Ad Analyzer tools Inspect

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.