Influence

Read scheduled times

scheduleList

Read-onlyIdempotent

Returns compact paginated calendar entries in an inclusive UTC date window, ordered by scheduled time. Entries contain campaign identity, status and timing without content or media. Reading available times does not reserve them.

Input Schema

TableJSON Schema

Name	Required	Description
`endAt`	Yes	Inclusive UTC epoch milliseconds, at most 366 days after startAt.
`limit`	No
`cursor`	No
`startAt`	Yes	Inclusive UTC epoch milliseconds.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026

changedOutput schema / oneOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "ok": {
-        "const": true,
-        "type": "boolean"
-      },
-      "output": {
-        "additionalProperties": false,
-        "properties": {
-          "cursor": {
-            "anyOf": [
-              {
-                "maxLength": 4096,
-                "type": "string"
-              },
-              {
-                "type": "null"
-              }
-            ]
-          },
-          "done": {
-            "type": "boolean"
-          },
-          "items": {
-            "items": {
-              "$ref": "#/$defs/__schema0"
-            },
-            "maxItems": 20,
-            "type": "array"
-          }
-        },
-        "required": [
-          "cursor",
-          "done",
-          "items"
-        ],
-        "type": "object"
-      },
-      "toolName": {
-        "const": "scheduleList",
-        "type": "string"
-      }
-    },
-    "required": [
-      "ok",
-      "output",
-      "toolName"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "error": {
-        "additionalProperties": false,
-        "properties": {
-          "code": {
-            "enum": [
-              "INVALID_INPUT",
-              "FORBIDDEN",
-              "NOT_FOUND",
-              "CONFLICT",
-              "FEATURE_DISABLED",
-              "CONFIRMATION_REQUIRED",
-              "CONFIRMATION_INVALID",
-              "UPSTREAM_FAILED",
-              "NEEDS_REVIEW",
-              "INTERNAL"
-            ],
-            "type": "string"
-          },
-          "message": {
-            "maxLength": 2048,
-            "minLength": 1,
-            "type": "string"
-          },
-          "retryable": {
-            "type": "boolean"
-          }
-        },
-        "required": [
-          "code",
-          "message",
-          "retryable"
-        ],
-        "type": "object"
-      },
-      "ok": {
-        "const": false,
-        "type": "boolean"
-      },
-      "toolName": {
-        "const": "scheduleList",
-        "type": "string"
-      }
-    },
-    "required": [
-      "error",
-      "ok",
-      "toolName"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "ok": {
+        "const": true,
+        "type": "boolean"
+      },
+      "output": {
+        "additionalProperties": false,
+        "properties": {
+          "cursor": {
+            "anyOf": [
+              {
+                "maxLength": 4096,
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "done": {
+            "type": "boolean"
+          },
+          "items": {
+            "items": {
+              "$ref": "#/$defs/__schema0"
+            },
+            "maxItems": 20,
+            "type": "array"
+          }
+        },
+        "required": [
+          "cursor",
+          "done",
+          "items"
+        ],
+        "type": "object"
+      },
+      "toolName": {
+        "const": "scheduleList",
+        "type": "string"
+      }
+    },
+    "required": [
+      "ok",
+      "output",
+      "toolName"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "error": {
+        "additionalProperties": false,
+        "properties": {
+          "code": {
+            "enum": [
+              "AI_SCHEDULING_LIMIT_REACHED",
+              "AI_SCHEDULING_UNAVAILABLE",
+              "INVALID_INPUT",
+              "FORBIDDEN",
+              "NOT_FOUND",
+              "CONFLICT",
+              "FEATURE_DISABLED",
+              "CONFIRMATION_REQUIRED",
+              "CONFIRMATION_INVALID",
+              "UPSTREAM_FAILED",
+              "NEEDS_REVIEW",
+              "INTERNAL"
+            ],
+            "type": "string"
+          },
+          "message": {
+            "maxLength": 2048,
+            "minLength": 1,
+            "type": "string"
+          },
+          "retryable": {
+            "type": "boolean"
+          }
+        },
+        "required": [
+          "code",
+          "message",
+          "retryable"
+        ],
+        "type": "object"
+      },
+      "ok": {
+        "const": false,
+        "type": "boolean"
+      },
+      "toolName": {
+        "const": "scheduleList",
+        "type": "string"
+      }
+    },
+    "required": [
+      "error",
+      "ok",
+      "toolName"
+    ],
+    "type": "object"
+  }
+]

First observedOct 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real value: entries are compact and exclude content/media, results are paginated and time-ordered, and reads do not reserve slots. It omits anything about the 366-day window bound or cursor expiry, but covers the key behavioral traits.

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 tight sentences, front-loaded with the return shape, then entry contents, then the non-reservation caveat. No filler; every sentence carries distinct 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 an output schema present, return values need no further explanation, and annotations carry the safety profile. The description supplies ordering, scope, exclusions and the non-reservation behavior, so an agent has enough to call it 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 coverage is only 50% — startAt/endAt carry format and range constraints, while limit (max 20) and cursor (maxLength) are undocumented. The description's 'paginated' and 'inclusive UTC date window' partially compensate but add no bounds or cursor-usage detail, so baseline 3 is right.

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?

States a specific verb+resource: returns compact paginated calendar entries ordered by scheduled time, scoped to an inclusive UTC date window. An agent knows exactly what comes back. It does not name a sibling, but the 'reading does not reserve' framing implicitly separates it from the schedule-execute tools.

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?

There is no explicit 'use this when / use X instead' statement, but 'Reading available times does not reserve them' implies this is a non-mutating inspection call distinct from reserving or executing schedules. Usage is implied rather than spelled out.

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

All Influence 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?