Skip to main content
Glama

Supovia Customer Support

by com.supovia
OverviewDiscussionsAdmin

List help-center articles

list_documents
Read-onlyIdempotent

Use this when someone asks which help articles or support docs exist, optionally for one website, language or article. Returns each article's id, title, slug, language, website and published flag, most recently edited first, 20 per page by default, without the article text. Not for finding articles about a topic.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoArticles per page, from 1 to 50; defaults to 20
cursorNoThe page.nextCursor of the previous page with the same filters; absent for the first page
localeNoOnly articles in this language code, e.g. en, it or fr; every language when absent
websiteIdNoOnly articles on this website; every website when absent
slugOriginalNoOnly the language versions of one article: its original slug before translation

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYeshasMore is true when more articles follow; pass nextCursor as cursor to get them
documentsYesArticle metadata, most recently edited first. Document content, embeddings, prompts, organization ids and arbitrary metadata are excluded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Opaque pagination cursor from a previous call"New value: +"The page.nextCursor of the previous page with the same filters; absent for the first page"
    • addedInput schema / properties / limit / description
      Added value: +"Articles per page, from 1 to 50; defaults to 20"
    • changedInput schema / properties / locale / description
      Previous value: -"Filter by locale (e.g. en, it, fr)"New value: +"Only articles in this language code, e.g. en, it or fr; every language when absent"
    • changedInput schema / properties / slugOriginal / description
      Previous value: -"Filter by original slug (base slug before localization)"New value: +"Only the language versions of one article: its original slug before translation"
    • changedInput schema / properties / websiteId / description
      Previous value: -"Filter by website id"New value: +"Only articles on this website; every website when absent"
    • addedOutput schema / properties / documents / description
      Added value: +"Article metadata, most recently edited first. Document content, embeddings, prompts, organization ids and arbitrary metadata are excluded."
    • addedOutput schema / properties / page / description
      Added value: +"hasMore is true when more articles follow; pass nextCursor as cursor to get them"
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, non-destructive). The description adds substantial beyond-annotation behavior: sort order (most recently edited first), default page size (20 per page), and that article text is excluded from results. It doesn't state total counts or cursor exhaustion behavior, keeping it from a 5.

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?

Three sentences, no filler, front-loaded with the use condition, then the return shape, then the negative routing. Every clause earns its place.

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?

With annotations covering safety and an output schema covering return structure, the description needn't explain return values, yet it usefully summarizes the returned fields and pagination default. Complete enough to call correctly; a minor gap remains around total-count or last-page signaling.

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 every parameter is already documented. The description restates the filterable dimensions (website, language, article) but adds no syntax, format, or edge-case detail beyond the schema. Baseline 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?

Specific verb+resource ('list help-center articles') with scope clarified ('without the article text'). Explicitly distinguishes from the sibling search_documents by stating 'Not for finding articles about a topic,' so an agent can route correctly.

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?

Provides a clear when-to-use trigger ('when someone asks which help articles exist') and an explicit when-not-to-use exclusion naming the topic-search alternative's domain. Both directions of the routing decision are stated.

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

All Supovia Customer Support toolsInspect
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.

Resources