list_sitesList all Webflow sites accessible to the connected account. Returns each site's id, display name, short name, preview URL, last published time, and custom domains. Use to discover which Webflow sites are available before reading their CMS collections or site content.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / examplesAdded value: +[
+ {}
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. Description adds value by specifying exactly what fields are returned (id, display name, short name, preview URL, last published time, custom domains). 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with purpose, no wasted words. Every sentence is informative and earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Low complexity tool with no parameters and no output schema. Description fully explains the return fields and intended use. No missing information for an agent to select and invoke correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters are defined; schema coverage is trivially 100%. With zero parameters, baseline is 4. Description does not need to add further parameter information.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states 'List all Webflow sites accessible to the connected account' using a specific verb and resource. It distinguishes from siblings like 'get_site' (single site) and 'list_collections' (collections of a site) by focusing on discovery.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly advises using this tool 'to discover which Webflow sites are available before reading their CMS collections or site content.' This provides clear context, though it does not explicitly list when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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 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.
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.
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.