The Revenue AI Report

List skills

list_skills

Read-onlyIdempotent

Browse The Revenue AI Report skill library: repeatable AI jobs for revenue teams, each with a ready prompt, a process, decision rules, and limitations. Filter by role, task, or level.

Input Schema

TableJSON Schema

Name	Required	Description
`role`	No	Filter by the role the skill is written for.
`task`	No	Filter by the job the skill finishes.
`level`	No	Filter by difficulty.
`limit`	No
`query`	No	Optional keyword filter on name and outcome.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`total`	Yes
`skills`	Yes
`returned`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 22, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "returned": {
+      "type": "number"
+    },
+    "skills": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "level": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "outcome": {
+            "type": "string"
+          },
+          "roles": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "setupTime": {
+            "type": "string"
+          },
+          "skillFileUrl": {
+            "type": "string"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "task": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "slug",
+          "name",
+          "outcome",
+          "roles",
+          "task",
+          "level",
+          "setupTime",
+          "url",
+          "skillFileUrl"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "returned",
+    "skills"
+  ],
+  "type": "object"
+}

First observedSep 22, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already cover the safety profile with readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful context about what skills contain (prompt, process, decision rules, limitations) but does not disclose additional operational behavior such as pagination, result ordering, or whether partial matches are returned. It does not contradict the annotations.

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?

The description is two sentences, front-loads the purpose, and uses no filler. Every sentence contributes either the scope of the library or the available filtering behavior.

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?

Given the annotations, output schema, and relatively simple optional-filter design, the description is largely complete: it defines the domain and the main filter choices. Minor gaps remain around the meaning of limit and when to use get_skill for more detail, but these are not critical for correct invocation.

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 80%, and the description only restates the role/task/level filters already documented in the schema. It adds no new meaning for the limit parameter or the query parameter, so the description provides limited additional value beyond the structured schema.

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?

The description clearly identifies a specific resource (the Revenue AI Report skill library) and a specific action (browse/filter), plus the filter dimensions role, task, and level. It does not explicitly differentiate from sibling list tools, but the resource type 'skills' is distinct enough to make the purpose unambiguous.

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 by the verb 'Browse' and the filtering language, so an agent can infer this is for discovering skills. However, there is no explicit guidance about when to prefer this over related tools like get_skill, list_prompts, or search_site, and no exclusions are stated.

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

All The Revenue AI Report 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.

Resources

Need Help?