Skip to main content
Glama

List articles

list_articles
Read-onlyIdempotent

List published article summaries, newest publication first, optionally filtered by topic and format. Returns page, total_items, total_pages and items with slugs, canonical URLs, excerpts and dates. Defaults to page 1 with 10 records; use search for a question or keywords, then get_article for full text.

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

NameRequiredDescriptionDefault
pageNoPage number, starting at 1 (default 1, maximum 500). Keep filters and limit unchanged while paging; stop at total_pages. A page beyond the results returns an empty items array.
limitNoRecords per page, from 1 to 20 (default 10). Use page to continue; total_items and total_pages describe all matches.
topicNoMatch this editorial topic exactly. Omit for all topics; combines with format.
formatNoMatch this article format exactly. Omit for all formats; combines with topic.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / format / description
      Added value: +"Match this article format exactly. Omit for all formats; combines with topic."
    • addedInput schema / properties / limit / description
      Added value: +"Records per page, from 1 to 20 (default 10). Use page to continue; total_items and total_pages describe all matches."
    • addedInput schema / properties / page / description
      Added value: +"Page number, starting at 1 (default 1, maximum 500). Keep filters and limit unchanged while paging; stop at total_pages. A page beyond the results returns an empty items array."
    • addedInput schema / properties / topic / description
      Added value: +"Match this editorial topic exactly. Omit for all topics; combines with format."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare the read-only, idempotent, non-destructive, closed-world profile. The description adds useful behavioral context beyond that: only published articles are returned, results are newest-first, pagination defaults to page 1 with 10 records, and the response fields are described.

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 front-loaded with the core purpose, then briefly covers return shape, defaults, and alternative tools. Every sentence contributes useful information without wasted text.

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

Completeness5/5

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

Given rich annotations and 100% schema coverage, the description fills the remaining gap by explaining the return fields and defaults despite there being no output schema. An agent has enough information to select and invoke the tool correctly.

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%, so the schema already carries detailed parameter semantics, including enums, defaults, and paging constraints. The description adds only a brief mention of optional topic and format filters and the default page size, which repeats what the schema already documents.

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 names a specific verb and resource: it lists published article summaries, with sorting and optional filters. It also distinguishes itself from siblings by directing users to search for questions or keywords and get_article for full text.

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

Usage Guidelines5/5

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

It explicitly states when to use this tool versus alternatives: use list_articles for published summaries, search for a question or keywords, and get_article for full text. The optional filtering and pagination defaults are also clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources