Skip to main content
Glama
srgplus

srgplus-mcp

Official
by srgplus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_contents

Read-only

Retrieve content items and collections from a hub profile workspace with pagination, filtering by type, archive status, and exclusions.

Instructions

List content items in a hub profile with cursor-based pagination.

workspace_id: target workspace ID — get available IDs from list_workspaces()
types: ["Content"], ["Collection"], or None for both (default)
Returns {"items": [...], "cursor": "..." | null}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typesNo
cursorNo
page_sizeNo
workspace_idYes
only_archivedNo
hub_profile_idYes
exclude_contentsNo
exclude_categoriesNo
exclude_collectionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.18

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already indicate read-only and non-destructive. Description adds context about cursor-based pagination and return shape, which is useful. No contradiction.

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?

Description is short, direct, and well-organized. It lists parameters and return shape without unnecessary detail.

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

Completeness2/5

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

Given the complexity (9 parameters) and no output schema, the description is incomplete. It covers only two parameters and omits details on filters, pagination behavior, and error handling.

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

Parameters2/5

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

Schema description coverage is 0%, and description only explains workspace_id and types out of 9 parameters. Many parameters like only_archived, exclude_contents are left undocumented, so description does not compensate for lack of schema descriptions.

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?

Clearly states the action (list) and resource (content items) within a scope (hub profile) and mentions pagination. Differentiates from sibling tools like search_contents and get_content by the nature of listing all items.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives like search_contents or get_content. It provides some parameter hints but lacks specific use-case direction.

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

Deploy Server

Other Tools