The Revenue AI Report

List prompts

list_prompts

Read-onlyIdempotent

Browse the public prompt library from The Revenue AI Report. Copy-ready AI prompts for revenue teams, filterable by team, category, or keyword. Use get_prompt to read the full prompt text.

Input Schema

TableJSON Schema

Name	Required	Description
`team`	No	Filter by revenue team.
`limit`	No	Default 30.
`query`	No	Keyword filter on name and summary.
`category`	No	Filter by what the prompt does.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`total`	Yes
`matched`	Yes
`prompts`	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": {
+    "matched": {
+      "type": "number"
+    },
+    "prompts": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "category": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "summary": {
+            "type": "string"
+          },
+          "teams": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "slug",
+          "name",
+          "summary",
+          "category",
+          "teams",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "returned": {
+      "type": "number"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "matched",
+    "returned",
+    "prompts"
+  ],
+  "type": "object"
+}

First observedSep 22, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds that the library is 'public' and 'copy-ready', which gives useful context beyond the structured hints. No contradiction.

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, purposeful sentences. The main action is front-loaded, and each sentence adds value: purpose, content/filters, and a sibling pointer. No wasted words.

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?

With a complete output schema and 100% parameter coverage, the description provides sufficient guidance for an agent to call it correctly. It clarifies the resource scope and points to the right sibling for full content.

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%, with each parameter already well-documented. The description mentions 'filterable by team, category, or keyword' but adds no syntax or format details beyond what the schema provides. Baseline 3 is appropriate.

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?

The description opens with a specific verb ('Browse') and resource ('public prompt library'), and immediately distinguishes itself from get_prompt by noting that tool reads the full text. This clearly separates it from the many sibling list_* tools.

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?

It explicitly routes users to get_prompt for reading full prompt text, which is the main alternative. While it doesn't mention other list_* tools, the resource-specific naming makes the usage context clear enough.

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?