Brent Burgess

List everything published

list_content

Read-onlyIdempotent

Every post, case study and page the server can read, newest first, with each one’s sections. Filter with kind ("post", "case_study" or "page"). Pass an id to fetch to read it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_content"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	No	Only this kind: post, case_study or page

Output Schema

Name	Required	Description	Default
`count`	Yes	How many items are listed
`items`	Yes	Posts and case studies newest first, then pages

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 27, 2026

changedOutput schema / properties / items / items / properties / brief / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "built": {
-        "description": "What was built, in one sentence",
-        "maxLength": 200,
-        "type": "string"
-      },
-      "changed": {
-        "description": "What changed, in one sentence",
-        "maxLength": 200,
-        "type": "string"
-      },
-      "problem": {
-        "description": "The problem, in one sentence",
-        "maxLength": 200,
-        "type": "string"
-      }
-    },
-    "required": [
-      "problem",
-      "built",
-      "changed"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "built": {
+        "description": "What was built, in one sentence",
+        "maxLength": 200,
+        "type": "string"
+      },
+      "changed": {
+        "description": "What changed, in one sentence",
+        "maxLength": 200,
+        "type": "string"
+      },
+      "problem": {
+        "description": "The problem, in one sentence",
+        "maxLength": 200,
+        "type": "string"
+      },
+      "role": {
+        "description": "What Brent did, and what AI or others did, in one sentence",
+        "maxLength": 200,
+        "type": "string"
+      }
+    },
+    "required": [
+      "problem",
+      "built",
+      "role",
+      "changed"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / items / items / properties / brief / description

Previous value: -"A case study’s summary in three sentences; null for a post or page"New value: +"A case study’s summary in four sentences; null for a post or page"

First observedOct 20, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful behavior ('newest first', returns sections) but says nothing about result size, pagination, or truncation for a tool that lists 'everything' — a meaningful gap for a potentially large read.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with what is returned and its ordering. The trailing 'Pass an id to fetch to read it' is slightly ambiguous — it reads like a parameter of this tool rather than a pointer to a sibling — which costs a point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values needn't be detailed, and the single optional param is fully documented. The only shortfall is the absent guidance on result volume/pagination for an unfiltered 'list everything' call.

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 100% and the single optional 'kind' param has an enum with descriptions, so the schema carries the load. The description repeats the enum values without adding meaning beyond what the schema provides, which is the baseline case.

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 ('Every post, case study and page the server can read') and adds ordering ('newest first') plus granularity ('with each one's sections'). It distinguishes itself from the sibling fetch by naming it for single-item reads, though the differentiation is brief.

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?

Gives clear usage context: filter with kind, and use fetch (passing an id) to read a single item instead of listing. No explicit when-not conditions beyond that, but the routing to the sibling is actionable.

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

All Brent Burgess 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?