Kamaan

The set splits cleanly into a content domain (article/collection/site tools) and a clearly prefixed support domain (Support_*), and read operations (Browse/Read/Search) are distinguished by scope and defaults. The main overlap is Update_SEO_Fields being a strict subset of Edit_Article, and the asymmetric defaults (articles default to blog, collections default to help) plus content_kind parameters force an agent to reason carefully before choosing.

Casing is uniformly PascalCase_with_underscores, which is good, but the verb vocabulary is inconsistent: articles are read with Browse_Articles/Read_Article, sites with My_Sites/Site_Details, creation is Create_Collection but Write_Article, and updates are split between Edit_Article and Update_Collection/Update_SEO_Fields. Domain prefixes (Support_) are applied to only one half of the set, so naming style is readable but not predictable.

22 tools is at the heavy end of the comfortable band, and it results from bundling two fairly distinct products (CMS and support inbox) into one server. Each individual tool earns its place, but the total surface is larger than a single coherent server would suggest.

Article lifecycle is well covered (write, read, browse, search, edit, delete, translate, SEO fields), collections have full CRUD plus reordering, and the support side covers listing, reading, replying, drafts, and status changes. Gaps are minor: no taxonomy/tag or media handling for articles, no publish/unpublish primitive, and sites are read-only with no support-side assignment or tagging operations.