Perspective AI

automation_list

Read-onlyIdempotent

Lists every automation configured on a perspective with its trigger, channel (sensitive details redacted), execution mode, enabled state, schedule description, and recent error/success metadata.

Behavior:

Read-only.
Errors when the perspective is not found or you do not have access.
Sensitive parts of channel delivery (e.g., webhook auth headers, full URLs) are redacted before being returned.
has_error / last_error / last_error_at / failure_count appear only when there have been recent failures.

When to use this tool:

Auditing what's wired up on a perspective before adding more automations.
Finding an automation_id to feed into automation_update, automation_delete, or automation_test.
Diagnosing a failing automation via last_error / failure_count.

When NOT to use this tool:

Creating a new automation — use automation_create.
Toggling enabled or changing config — use automation_update.
Verifying delivery actually works — use automation_test.

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": {
      "workspace_id": "<workspace_id>",
      "perspective_id": "<perspective_id>"
    },
    "name": "automation_list"
  }
}

Input Schema

Name	Required	Description	Default
`workspace_id`	Yes	Workspace ID (from workspace_get_default or workspace_list) or workspace slug (uniqueName)
`perspective_id`	Yes	Perspective ID

Output Schema

Name	Required	Description	Default
`error`	No
`message`	Yes
`success`	Yes
`automations`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 31, 2026
- addedInput schema / properties / perspective_id / maxLength
```
Added value: +128
```
- addedInput schema / properties / workspace_id / maxLength
```
Added value: +128
```
Changed1 schema field changedOct 6, 2026
- removedOutput schema / properties / automations / items / properties / message_template
```
Removed value: -{
-  "type": "string"
-}
```

Changed2 schema fields changedSep 10, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed4 schema fields changedJul 21, 2026

changedOutput schema / properties / automations / items / properties / channel / description

Previous value: -"Redacted channel config"New value: +"Redacted delivery channel config"

changedOutput schema / properties / automations / items / properties / channel_type / description

Previous value: -"email, webhook, or the connected integration provider ID"New value: +"email, webhook, insights, or the connected integration provider ID"

addedOutput schema / properties / automations / items / properties / kind

Added value: +{
+  "enum": [
+    "delivery",
+    "insights"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / automations / items / required

Previous value: -[
-  "automation_id",
-  "name",
-  "enabled",
-  "trigger_type",
-  "execution_mode",
-  "trigger",
-  "channel_type",
-  "channel"
-]New value: +[
+  "automation_id",
+  "name",
+  "enabled",
+  "trigger_type",
+  "execution_mode",
+  "trigger",
+  "channel_type"
+]

Changed1 schema field changedJul 13, 2026
- changedOutput schema / properties / automations / items / properties / channel_type / description
```
Previous value: -"email, slack, hubspot, webhook"New value: +"email, webhook, or the connected integration provider ID"
```
Changed14 schema fields changedJun 25, 2026
- addedOutput schema / properties / automations / items / properties / condition / properties / tagsAll / anyOf
```
Added value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / automations / items / properties / condition / properties / tagsAll / items
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / automations / items / properties / condition / properties / tagsAll / type
```
Removed value: -"array"
```
- addedOutput schema / properties / automations / items / properties / condition / properties / tagsAny / anyOf
```
Added value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / automations / items / properties / condition / properties / tagsAny / items
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / automations / items / properties / condition / properties / tagsAny / type
```
Removed value: -"array"
```
- addedOutput schema / properties / automations / items / properties / condition / properties / trustScoreMax / anyOf
```
Added value: +[
+  {
+    "maximum": 100,
+    "minimum": 0,
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / automations / items / properties / condition / properties / trustScoreMax / maximum
```
Removed value: -100
```
- removedOutput schema / properties / automations / items / properties / condition / properties / trustScoreMax / minimum
```
Removed value: -0
```
- removedOutput schema / properties / automations / items / properties / condition / properties / trustScoreMax / type
```
Removed value: -"number"
```
- addedOutput schema / properties / automations / items / properties / condition / properties / trustScoreMin / anyOf
```
Added value: +[
+  {
+    "maximum": 100,
+    "minimum": 0,
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / automations / items / properties / condition / properties / trustScoreMin / maximum
```
Removed value: -100
```
- removedOutput schema / properties / automations / items / properties / condition / properties / trustScoreMin / minimum
```
Removed value: -0
```
- removedOutput schema / properties / automations / items / properties / condition / properties / trustScoreMin / type
```
Removed value: -"number"
```
AddedApr 27, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnlyHint/idempotentHint annotations, the description discloses that sensitive channel details (webhook auth headers, full URLs) are redacted before return, that the call errors when the perspective is missing or inaccessible, and that failure fields appear conditionally. These are non-obvious behaviors an agent must plan around.

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?

The lead sentence is front-loaded with the resource and returned fields, and the bulleted Behavior/When-to-use sections are scannable. It runs slightly long for a two-parameter read tool, but each bullet carries distinct information (redaction, conditional fields, sibling routing) rather than padding.

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?

An output schema exists so return values need no narrative, and the description instead covers the aspects schema cannot: error conditions, redaction policy, conditional failure metadata, and sibling routing. Nothing an agent needs to invoke and interpret this correctly is missing.

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?

With 100% schema description coverage, the schema already documents both required parameters, including the workspace slug alternative. The description adds no additional parameter-level meaning beyond referring to 'a perspective', so the baseline of 3 applies.

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 ('Lists every automation configured on a perspective') and enumerates the returned attributes: trigger, channel, execution mode, enabled state, schedule, error/success metadata. An agent can immediately distinguish this from sibling tools such as automation_create or automation_get-style reads.

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

Usage Guidelines5/5

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

Explicit 'When to use' and 'When NOT to use' sections name concrete scenarios (auditing, harvesting automation_id, diagnosing failures) and route the agent to automation_create, automation_update, and automation_test for the excluded cases.

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

All Perspective AI 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.