FeatureOS

List articles

list_articles

Read-only

List knowledge base articles with optional filtering and pagination. To find an article by keyword, use search_articles instead.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_articles"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number (default: 1).
`sort`	No	Time order: 'latest_created_at', 'oldest_created_at', 'latest_updated_at', or 'oldest_updated_at'. Omit for the default order.
`locale`	No	Filter by language code, e.g. 'en', 'es', 'fr', 'de'.
`status`	No	Filter by status: 'published', 'draft', or 'in_review'.
`tag_id`	No	Filter by tag ID.
`privacy`	No	Filter by privacy: 'public', 'unlisted', or 'private'.
`per_page`	No	Items per page (default: 30).
`author_id`	No	Filter by author ID.
`assignee_id`	No	Filter by assignee ID.
`collection_id`	No	Filter by collection ID.

Output Schema

Name	Required	Description	Default
`page`	No
`articles`	No
`has_more`	No
`per_page`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds only that filtering and pagination are supported; it does not mention result caps, filter combination behavior, or per_page limits (left entirely to the schema). With safety already documented structurally, a 3 fits.

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 sentences, zero filler, with the primary purpose front-loaded and the sibling routing placed immediately after. Nothing is repeated from the title or annotations.

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?

An output schema exists, annotations cover the safety profile, and all ten optional parameters are fully described in the schema, so the description does not need to restate them. A minor gap remains around how multiple filters combine (intersection) and whether filtering implies access-scoped visibility, but nothing an agent needs in order to call it is missing.

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% and every one of the ten parameters is documented inline with defaults, enums and ranges. The description contributes no additional parameter meaning beyond the generic phrase "optional filtering and pagination," so the baseline of 3 applies.

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?

States a specific verb and resource ("List knowledge base articles") plus the scope modifiers (optional filtering and pagination), and explicitly distinguishes itself from the search sibling. An agent can pick this over search_articles without inspecting either schema.

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?

Gives an explicit routing rule: keyword lookup belongs to search_articles, this tool is for enumeration. It does not address borderline cases such as when to use list_articles versus get_article for a known ID, so the guidance is clear but not exhaustive.

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

All FeatureOS tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.