Skip to main content
Glama

pages_list

Read-onlyIdempotent

Retrieve a list of pages from a Voog site with optional filters such as language, content type, or path prefix. Returns page details including id, path, title, 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 declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and the description adds 'Read-only' and lists returned fields, which aligns and adds value. No contradictions.

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 concise sentences, front-loaded with the purpose and key details. Every word is informative and no redundancy.

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 the absence of an output schema, the description adequately explains the fields returned and default behavior. However, it omits details on pagination, sorting behavior despite a sort parameter, and result format beyond fields.

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?

Schema coverage is 100% with clear descriptions for all parameters. The description adds meaning by stating default behavior (no filters returns everything) and listing the fields returned, which is not in 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 'List pages on the Voog site' specifying the verb and resource, and lists the returned fields. It distinguishes from sibling tools like 'page_get' by being a list operation.

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 mentions that all filters are optional and with no filters it returns every page, providing usage context. However, it does not explicitly compare to alternatives like 'page_get' 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/runnel/voog-mcp'

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