Skip to main content
Glama
rubenlangeweg

productive-mcp-rb2

list_pages

list_pages
Read-only

List knowledge base pages from Productive.io, filtered by project ID to show project-specific documentation. Limits results up to 200 pages.

Instructions

List knowledge base pages in Productive.io. Filter by project to see project-specific docs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNoFilter pages by project ID (optional — omit for all pages)
limitNoNumber of pages to return (1-200, default 30)
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the description is consistent but adds minimal extra context beyond stating it lists pages with optional filtering.

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 a single concise sentence that front-loads the purpose, with no wasted words.

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

Completeness3/5

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

Given no output schema, the description is adequate for a simple list tool with 2 parameters, but it could mention the return type or pagination.

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 description adds context for the project_id parameter by mentioning filtering, but does not add significant meaning beyond the schema.

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 lists knowledge base pages and mentions filtering by project. It distinguishes itself from siblings like get_page and create_page.

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

Usage Guidelines3/5

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

The description implies using the filter for project-specific docs but does not explicitly guide when to use this tool versus alternatives like list_folders or other list tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rubenlangeweg/productive-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server