Skip to main content
Glama

Sleepwalker

by ai.sleepwalker
OverviewDiscussionsAdmin

List Sleepwalker visibility runs

list_sleepwalker_visibility_runs
Read-onlyIdempotent

List queued infrastructure AI Visibility runs for the authenticated user. When has_more is true, pass next_starting_after as starting_after to fetch the next page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of items to return.
statusNoOptional status filter. Common values are queued, running, completed, failed, and cancelled.
starting_afterNoPagination cursor: pass the previous page's next_starting_after to fetch the next page.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / starting_after
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Pagination cursor: pass the previous page's next_starting_after to fetch the next page.",
+  "title": "Starting After"
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of items to return."
    • addedInput schema / properties / status / description
      Added value: +"Optional status filter. Common values are queued, running, completed, failed, and cancelled."
  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 indicate readOnly and idempotent. Description adds context that it lists 'queued' runs, but does not detail any side effects beyond what annotations cover.

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?

Two succinct sentences: first states purpose, second provides critical pagination usage. No redundant information.

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 3 well-described parameters, an output schema, and clear pagination guidance, the description is fully adequate for an agent to use the tool correctly.

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 has 100% description coverage for all parameters, so the tool description does not need to add much. It mentions pagination but does not elaborate on parameter meanings beyond schema.

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?

Description specifies 'List queued infrastructure AI Visibility runs for the authenticated user', which is a clear verb+resource pair and differentiates from sibling tools like list_sleepwalker_content_runs.

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?

Provides explicit pagination guidance ('When has_more is true, pass next_starting_after as starting_after'), but does not contrast with alternative tools for similar tasks.

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

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