postnext

List mini sites

list_mini_sites

Read-only

List the bio pages (mini sites) belonging to the currently selected team, with their public URL, publish state and setup progress. Use this first when the user mentions "my bio page", "link in bio" or "mini site" — every other mini-site tool takes the siteId this returns (and can omit it entirely when the team has exactly one site). suspended: true means PostNext took that page offline; it cannot be published again until support reviews it (support@postnext.io).

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`hint`	No
`sites`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 10, 2026

addedOutput schema / properties / sites / items / properties / suspended
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / properties / sites / items / required

Previous value: -[
-  "id",
-  "published",
-  "setup"
-]New value: +[
+  "id",
+  "published",
+  "suspended",
+  "setup"
+]

Changed1 schema field changedOct 2, 2026
- removedOutput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
First observedSep 22, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already establish the safe read-only, closed-world profile, but the description goes further with a domain-specific rule: suspended: true means PostNext took the page offline and it cannot be republished until support reviews it. That is real behavioral context an agent could not infer from the schema or annotations.

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 sentences, front-loaded with purpose, then usage routing, then the suspended-state caveat. No redundancy and no filler; each 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?

An output schema exists so return values need not be enumerated, yet the description still names the key fields and the one field (suspended) whose semantics are non-obvious. Combined with the routing guidance, an agent has everything needed to select and call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so there is no argument syntax to clarify; the description instead explains the implicit team scope of the result set. The 0-parameter baseline applies, and the team-scoping note is a small positive addition.

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?

States a specific verb (List) and resource (bio pages / mini sites) scoped to the currently selected team, and enumerates what each entry carries (public URL, publish state, setup progress). This clearly distinguishes it from the single-site sibling get_mini_site.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to call it first when the user mentions "my bio page", "link in bio" or "mini site", and explains the downstream contract: every other mini-site tool consumes the siteId returned here, which may be omitted when the team has exactly one site. Nothing is left to inference.

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

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