Opsphere — DevOps & SRE Intelligence

Cloudflare: list Logpush jobs

cf_logpush_jobs_list

Read-only

List Logpush jobs for a zone (destination, dataset, enabled). Includes edgeHttpForensics: whether http_requests Logpush exists and recommended Datadog queries for EdgeResponseStatus / RayID. Use this before blaming app logs for edge redirects; cf_firewall_events and cf_http_security_* are not HTTP response forensics.

Input Schema

Name	Required	Description
`zone`	Yes	Zone name (e.g. your-tenant.com) or zone ID
`context_id`	No	Optional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.
`account_slug`	No	Cloudflare account slug. Required when the workspace has multiple accounts and the zone is not yet cataloged.
`environment_slug`	No	Cloud Catalog environment used as an account-routing preference when no zone is provided.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	Yes
`contractVersion`	Yes
`dataSchemaVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

addedOutput schema / properties / data / properties / edgeHttpForensics

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "datadogDestinations": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "gaps": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "hasEnabledHttpPush": {
+      "type": "boolean"
+    },
+    "hasHttpRequestDataset": {
+      "type": "boolean"
+    },
+    "nextSteps": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "otherDestinations": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "recommendedDdQueries": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "s3Destinations": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "warnings": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "zoneHint": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "hasHttpRequestDataset",
+    "hasEnabledHttpPush",
+    "datadogDestinations",
+    "s3Destinations",
+    "otherDestinations",
+    "recommendedDdQueries",
+    "nextSteps",
+    "gaps",
+    "warnings"
+  ],
+  "type": "object"
+}

Changed16 schema fields changedOct 26, 2026

changedOutput schema / properties / data / additionalProperties
```
Previous value: -trueNew value: +false
```
removedOutput schema / properties / data / properties / count
```
Removed value: -{
-  "type": "number"
-}
```

removedOutput schema / properties / data / properties / errors

Removed value: -{
-  "items": {
-    "$ref": "#/properties/data/properties/result/anyOf/0/items"
-  },
-  "type": "array"
-}

addedOutput schema / properties / data / properties / gaps

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

removedOutput schema / properties / data / properties / items

Removed value: -{
-  "$ref": "#/properties/data/properties/result/anyOf/0"
-}

addedOutput schema / properties / data / properties / jobs

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "dataset": {
+        "type": "string"
+      },
+      "destinationConf": {
+        "type": "string"
+      },
+      "enabled": {
+        "type": "boolean"
+      },
+      "id": {
+        "type": "integer"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

removedOutput schema / properties / data / properties / messages

Removed value: -{
-  "items": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "$ref": "#/properties/data/properties/result/anyOf/0/items"
-      }
-    ]
-  },
-  "type": "array"
-}

addedOutput schema / properties / data / properties / partial
```
Added value: +{
+  "type": "boolean"
+}
```

removedOutput schema / properties / data / properties / result

Removed value: -{
-  "anyOf": [
-    {
-      "items": {
-        "additionalProperties": true,
-        "properties": {},
-        "type": "object"
-      },
-      "type": "array"
-    },
-    {
-      "$ref": "#/properties/data/properties/result/anyOf/0/items"
-    }
-  ]
-}

removedOutput schema / properties / data / properties / result_info

Removed value: -{
-  "$ref": "#/properties/data/properties/result/anyOf/0/items"
-}

removedOutput schema / properties / data / properties / success
```
Removed value: -{
-  "type": "boolean"
-}
```
addedOutput schema / properties / data / properties / truncated
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / data / properties / warnings

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / data / required

Added value: +[
+  "jobs",
+  "partial",
+  "truncated",
+  "warnings",
+  "gaps"
+]

addedOutput schema / properties / dataSchemaVersion

Added value: +{
+  "const": 2,
+  "type": "number"
+}

changedOutput schema / required

Previous value: -[
-  "contractVersion",
-  "ok",
-  "data"
-]New value: +[
+  "contractVersion",
+  "dataSchemaVersion",
+  "ok",
+  "data"
+]

First observedOct 15, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The readOnly and non-destructive annotations already cover the safety profile, so the description adds useful behavioral context by disclosing the edgeHttpForensics output and its recommended Datadog queries. It does not cover permissions, pagination, or freshness behavior, but for a read-only list with an output schema this is solid.

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 three sentences with zero waste, front-loading the core action and scope before the specialized forensic context and sibling caveat. Every sentence adds actionable 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?

Given the annotations, complete parameter schema, and an output schema, the description is sufficient for correct invocation. It also supplies the key situational context about edge redirects and the relevant alternative tools.

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%, so all four parameters are already documented in the input schema. The description reinforces the zone scope but does not add syntax or routing details for context_id, account_slug, or environment_slug beyond what the schema provides.

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 verb and resource ('List Logpush jobs') and scopes it to a zone. It also calls out included fields and the special edgeHttpForensics payload, making the tool's purpose distinct from basic list operations.

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 gives a clear usage scenario ('Use this before blaming app logs for edge redirects') and explicitly names cf_firewall_events and cf_http_security_* as unsuitable for HTTP response forensics. It stops short of a complete when-to-use/when-not matrix but provides strong contextual routing.

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

All Opsphere — DevOps & SRE Intelligence 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?