Skip to main content
Glama

pages_list

Read-onlyIdempotent

Retrieve pages from a Voog site with optional filters for language, type, path, search, and parent. Returns page ID, path, title, hidden status, and layout name.

Instructions

List pages on the Voog site (id, path, title, hidden, layout name). All filters are optional; with no filters this returns every page. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteYesSite name from voog_list_sites
language_codeNoFilter by language code (e.g. 'et', 'en')
content_typeNoFilter by page type. Voog accepts 'page', 'blog', 'elements', 'link'.
node_idNoFilter to pages on a specific node (parallel-translation group)
path_prefixNoPages whose path starts with this prefix (e.g. '/blog')
searchNoFree-text search across title, menu_title, description, path
parent_idNoFilter to direct children of a specific parent page id
language_idNoFilter by language id (use language_code for the human-readable form)
sortNoVoog sort string: '<object>.<attr>.<$asc|$desc>'. Examples: 'page.title.$asc', 'page.created_at.$desc'.
filtersNoEscape hatch for Voog filter keys not exposed as typed args. Keys MUST match q.page.<attr>.(\$eq|\$cont|\$gteq|\$lteq|\$gt|\$lt|\$in|\$nin|\$starts|\$ends|\$null|\$has). Values are pass-through. Merged with typed args; filter keys override typed-arg-derived keys on collision.
Behavior4/5

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

Annotations already provide readOnly, destructive, and idempotent hints. Description adds 'Read-only' and lists returned fields, adding minor value beyond 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?

Two efficient sentences; first states purpose and returned fields, second clarifies filters and read-only nature. No wasted words.

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?

Given no output schema, description mentions returned fields but could be more detailed on pagination or full structure. However, sibling tools and schema parameters provide sufficient context.

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 covers 100% of parameters with descriptions. Description only mentions that fields like id, path, title are returned, adding some meaning but not compensating for low coverage.

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 'List pages on the Voog site' with specific resource and action. Mentions returned fields and distinguishes from sibling list tools.

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?

States that all filters are optional and that no filters return every page, providing clear context for use. Does not explicitly mention when not to use or alternatives, but purpose is clear.

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/runnel/voog-mcp'

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