Skip to main content
Glama

Webflow

by io.github.pipeworx-io

List Collection Items

list_collection_items
Read-onlyIdempotent

List the items (records) in a Webflow CMS collection — the live site content such as blog posts, products, or team members. Returns paginated items with their id, draft/archived status, last published time, and fieldData (the CMS field values). Use to read the actual content stored in a Webflow collection.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of items to return (default 50, max 100).
offsetNoNumber of items to skip for pagination (default 0).
collection_idYesThe id of the Webflow CMS collection whose items to list (from list_collections).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "collection_id": "614b3f2a9c1d4e5f2a8c9d0e"
+  },
+  {
+    "collection_id": "614b3f2a9c1d4e5f2a8c9d0e",
+    "limit": 25,
+    "offset": 50
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds value by explaining the return structure (paginated items with id, status, timestamps, fieldData) and pagination behavior, which goes beyond annotations.

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 that front-load the core purpose with examples, no wasted words. Efficient and clear.

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 operation with three well-documented parameters and no output schema, the description adequately covers the return structure and pagination. Lacks mention of error handling or rate limits but is sufficient.

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 coverage is 100%, so baseline is 3. The description does not add additional meaning to parameters beyond what the schema provides; it mentions collection_id implicitly but no extra detail.

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 clearly states the tool lists items in a Webflow CMS collection, providing examples like blog posts and products. It distinguishes itself from siblings such as get_collection_item and list_collections by specifying it returns live site content.

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?

The description explicitly says 'Use to read the actual content stored in a Webflow collection,' setting clear context for when to use. It does not mention alternatives or when not to use, but the context is sufficient for a read-only tool.

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

All Webflow toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation2/5

Several tools have blurry boundaries: ask_pipeworx and ask_pipeworx_beta are explicitly identical right now, polymarket_edges/polymarket_arbitrage/polymarket_edge_tracker/polymarket_fill_risk all target overlapping prediction-market signals, and ai_visibility_check vs scan_competitor_ai_presence plus entity_profile vs recent_changes vs compare_entities partially duplicate each other. The Webflow tools are distinct, but the dominant Pipeworx cluster is hard to navigate.

Naming Consistency2/5

Naming mixes multiple conventions: clean verb_noun for Webflow tools (list_sites, get_collection_item), an ask_pipeworx family, plain single verbs (remember, recall, forget), and long noun-cluster names for prediction markets (polymarket_arbitrage, polymarket_edge_tracker). There is no single predictable pattern across the set.

Tool Count1/5

36 tools is excessive for a server named 'Webflow' — only about six tools actually concern the Webflow CMS (list_sites, get_site, list_collections, list_collection_items, get_collection_item, generate_llms_txt). The remaining ~30 tools form a completely different data-research/prediction-market/memory suite, making the server wildly over-scoped and mislabeled.

Completeness2/5

For the Webflow domain, the surface is read-only: sites and collections can be listed and items fetched, but there are no create, update, delete, or publish operations, leaving obvious lifecycle gaps. The extensive non-Webflow tools do not address the stated server purpose, so the mismatch hurts completeness rather than fixing it.

Resources