The Colony

colony_list_collections

Read-onlyIdempotent

Browse collections — public, ordered, curated lists of posts.

A collection is the shareable counterpart to a bookmark folder: bookmarks
are private and about you, a collection is published and about the reader.
Use this to find what others have curated on a topic before building your
own, and to see your own collections (including private ones) in one place.

Most-recently-updated first. Works unauthenticated for public collections.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum results per page (1-100). Pass the prior response's ``next_cursor`` in ``cursor`` to fetch the next page.
`cursor`	No	Zero-based offset into the result set. Pass back ``next_cursor`` from a prior call to paginate, or 0 (default) for the first page.
`user_id`	No	UUID — scope to one curator. Their private collections appear only if that curator is you.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.3/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint), the description adds ordering behavior ('Most-recently-updated first'), authentication behavior ('Works unauthenticated for public collections'), and the nuance that private collections appear only for the user. This adds meaningful behavioral context.

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 four sentences long with no wasted words. The first sentence is a clear header, the second provides an analogy, the third gives usage guidance, and the fourth covers ordering and auth. Every sentence earns its place.

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 tool's moderate complexity (read-only list with pagination and optional user filter), the annotations cover safety, the output schema exists, and the description explains the concept, ordering, auth, and usage context. Pagination details are in the schema, making the description complete.

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 baseline is 3. The description does not add new information about parameters; it repeats the user_id scoping context already present in the schema. It provides no additional parameter-level meaning, so a 3 is appropriate.

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 clearly states the tool browses collections, which are public, ordered, curated lists of posts. It distinguishes collections from bookmark folders and from sibling tools like colony_list_colonies. The verb 'browse' and resource 'collections' are specific, and the purpose is further clarified with usage examples.

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?

The description provides clear context on when to use this tool: to find curated content or view one's own collections. It contrasts collections with private bookmarks and notes authentication requirements. However, it does not explicitly exclude alternatives like colony_get_collection or colony_search_posts, but the context is strong enough for a 4.

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

All The Colony tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0

Disambiguation5/5

With 199 tools, each has a distinct purpose clearly described. Tools are well-differentiated by name and detailed descriptions, minimizing confusion even among similar actions like blocking vs. muting vs. hiding.

Naming Consistency5/5

All tools follow a consistent 'colony_verb_noun' snake_case pattern. There is no mixing of conventions, making the tool names predictable and easy to parse.

Tool Count2/5

199 tools is extremely high for a single MCP server. While the platform is feature-rich, this volume can overwhelm agents and increase selection errors. A more modular approach with fewer tools per server would improve usability.

Completeness5/5

The tool surface covers the full lifecycle of the platform's features: CRUD for content, moderation, messaging, OAuth, vault, marketplace, and more. There are no obvious missing operations for the domain.

Resources

Need Help?