Skip to main content
Glama

Webflow

by io.github.pipeworx-io

Get Collection Item

get_collection_item
Read-onlyIdempotent

Get a single item (record) from a Webflow CMS collection by its id. Returns the item's id, draft/archived status, last published time, and fieldData (the full CMS field values). Use after list_collection_items to read one piece of Webflow site content in detail.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYesThe id of the CMS item to retrieve (from list_collection_items).
collection_idYesThe id of the Webflow CMS collection containing the item (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",
+    "item_id": "72e5c8f1a2b3d4e5f6g7h8i9"
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the description is not required to repeat those. It adds value by describing the return structure (draft/archived status, fieldData), which provides behavioral context beyond annotations. No contradictions.

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 action and resource, minimal waste. Every sentence adds value, including the usage hint and return field list.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (2 required params, no nested objects, no output schema), the description covers purpose, usage, and return fields adequately. Annotations handle the safety profile. No gaps for a read-only retrieval tool.

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?

Schema coverage is 100%, with each parameter having a description. The description enhances this by connecting the parameter origin (e.g., item_id from list_collection_items, collection_id from list_collections), adding contextual meaning beyond the schema.

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 gets a single item from a Webflow CMS collection by ID, and specifies the returned fields (id, draft/archived status, last published time, fieldData). It distinguishes itself from list_collection_items, 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?

States 'Use after list_collection_items to read one piece of Webflow site content in detail,' giving explicit context for when to invoke. While it doesn't explicitly list alternatives, the usage guidance is clear and the sibling list includes the relevant listing tools.

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