Skip to main content
Glama

Revnu

by com.revnu
OverviewDiscussionsAdmin

List Block List

blocklist_list
Read-onlyIdempotent

The customer's block list, newest first: the domains and addresses their agent will never research or contact. Pass back nextCursor for the next page. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum block-list entries per page; default 50, range 1-200.
cursorNoOpaque nextCursor from the previous blocklist_list result. Omit for the first page.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
entriesYes
nextCursorYesPass to the next list call; null means the last page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedOutput schema / properties / entries / items / properties / addedAt / description
      Previous value: -"Unix epoch milliseconds."New value: +"When the block was added, as Unix epoch milliseconds."
    • addedOutput schema / properties / entries / items / properties / addedBy / description
      Added value: +"Recorded actor who added the block, or null when unknown."
    • addedOutput schema / properties / entries / items / properties / reason / description
      Added value: +"Why this identity was blocked, or null when not recorded."
  2. Changed3 schema fields changed
    • addedInput schema / properties / cursor / description
      Added value: +"Opaque nextCursor from the previous blocklist_list result. Omit for the first page."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum block-list entries per page; default 50, range 1-200."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "entries": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "addedAt": {
+            "description": "Unix epoch milliseconds.",
+            "type": "number"
+          },
+          "addedBy": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Block-list entry ID for blocklist_remove.",
+            "type": "string"
+          },
+          "kind": {
+            "description": "Blocked identity type, such as domain, email or LinkedIn profile.",
+            "type": "string"
+          },
+          "reason": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "source": {
+            "description": "Origin of the block; unsubscribe entries cannot be removed.",
+            "type": "string"
+          },
+          "value": {
+            "description": "Normalized identity that must not be contacted.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "kind",
+          "value",
+          "reason",
+          "source",
+          "addedBy",
+          "addedAt"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "nextCursor": {
+      "description": "Pass to the next list call; null means the last page.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "entries",
+    "nextCursor"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavior beyond annotations: results are ordered 'newest first' and pagination is handled by passing back the returned nextCursor. It does not mention auth requirements or rate limits, but those are less critical here.

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 compact sentences with no wasted words. The core purpose is front-loaded, followed by pagination behavior and the read-only nature.

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?

The tool is simple, has only two fully documented optional parameters, full annotation coverage, and an output schema. The description supplies ordering and pagination guidance, and since an output schema exists, it need not explain return values. Nothing essential is missing 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 100%, and the schema already explains both limit and cursor in detail. The description mentions nextCursor for pagination but adds no parameter semantics beyond what the schema provides, so it meets the baseline rather than exceeding it.

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 states a specific resource and scope: 'The customer's block list' with contents defined as 'the domains and addresses their agent will never research or contact.' It is clearly distinguishable from sibling list tools like leads_list, review_list, and workflows_list because the resource is explicitly the customer's block list.

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?

The description gives clear contextual cues: it is a read-only list, newest first, and instructs the agent to 'Pass back nextCursor for the next page.' It does not explicitly name when to use this tool versus alternatives, but no sibling tool overlaps with the block-list resource.

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

All Revnu 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