Skip to main content
Glama
vuluu2k

WebCake Storefront MCP

by vuluu2k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_articles

List blog article metadata with optional search by title/slug or category filter, returning only public, published posts.

Instructions

List blog articles (metadata only, without HTML content). Use get_article for the full content. Pass term to search by title/slug. Pass category_id to list the posts filed under one blog category — that view is the public one, so hidden posts and posts scheduled in the future are left out.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (default 1)
termNoSearch articles by title or slug
limitNoItems per page (default 20)
category_idNoFilter by blog category id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.31.10
    • changedInput schema / properties / category_id / description
      Previous value: -"Filter by category"New value: +"Filter by blog category id"
    • changedInput schema / properties / limit / description
      Previous value: -"Items per page"New value: +"Items per page (default 20)"
    • changedInput schema / properties / page / description
      Previous value: -"Page number"New value: +"Page number (default 1)"
    • addedInput schema / properties / term
      Added value: +{
+  "description": "Search articles by title or slug",
+  "type": "string"
+}
  2. First observedv1.31.8

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that results are metadata-only and that the category_id view excludes hidden and scheduled posts. However, it leaves ambiguous whether the default (no category_id) list includes such posts, and it does not mention pagination defaults or other response characteristics.

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, front-loaded with the core distinction (metadata only) and the alternative tool. The parameter guidance is integrated without excess, making it concise and well-organized.

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?

For a list tool with four parameters and no output schema, the description covers the essential points: metadata-only returns, the alternative for content, and parameter-specific behavior. Minor gaps like default filtering and pagination are not critical given the schema descriptions.

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?

The schema already documents all parameters with 100% coverage, but the description adds valuable context for term and category_id, particularly the public-filter behavior of category_id. This goes beyond the schema's brief descriptions.

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 states a clear verb ('List') and resource ('blog articles') and explicitly notes it returns only metadata, not HTML content. It distinguishes itself from get_article by naming the alternative for full content, making its purpose unambiguous.

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?

It explicitly directs users to get_article when full content is needed, and it explains the public-filter behavior of category_id. It does not, however, contrast with other sibling list tools like list_categories, but those are for different resources, so the guidance is adequate.

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

Deploy Server

Other Tools