Skip to main content
Glama
vuluu2k

WebCake Storefront MCP

by vuluu2k
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_articles

Read-only

Retrieve blog article metadata (no HTML), search by title or slug, or filter by category to show public posts only. Use get_article for full content.

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

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.1/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, so safety is covered. The description adds non-obvious behavior: category_id view is the public one and excludes hidden and future-scheduled posts. That visibility semantics is the kind of detail structured fields would not convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, each earning its place: scope, sibling routing, and parameter behavior. Front-loaded with the 'what' before the 'when'. Slightly wordy in the third sentence but no filler.

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?

Covers purpose, sibling relationship, and the non-obvious visibility filtering. With no output schema, the description should ideally hint at the return shape (article fields, pagination envelope), and it only says 'metadata only' – a small remaining gap.

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 page/limit/term/category_id are already documented. The description re-explains term and category_id without adding syntax, format, or default details beyond the schema. Baseline 3 is appropriate.

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 blog articles') with a disambiguating scope note ('metadata only, without HTML content'). It also distinguishes itself from the get_article sibling directly, which is more than most list tools do.

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?

Explicitly routes the agent to get_article for full content, and explains when to use term vs category_id. It does not cover pagination usage or when to prefer search_products-style alternatives, but for a listing tool the guidance is clear and actionable.

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