This server defines 23 tools with reasonable naming conventions and decent parameter schemas. However, there are significant gaps in descriptions, missing output schema documentation, and inconsistent parameter detail. Most tools follow verb_noun naming (create_webset, list_websets, get_webset, delete_webset), which is correct. Tool descriptions are present and non-trivial for most tools (e.g., create_webset: 'Create a new Webset collection...'), meeting the 10-1024 character guideline. However, several tools have minimal or missing descriptions (e.g., update_webset, get_webhook, update_webhook lack visible detailed descriptions in the source). Parameter schemas are visible for complex tools like create_webset and create_search, but output schemas are completely undocumented, the code shows tool registration but returns no structured documentation of response shapes. Error handling is not evident in the provided code excerpts. The server lacks tool annotations (readOnlyHint, destructiveHint, idempotentHint), which are marked as false in the feature list. This is a borderline C/D server: definitions exist and are mostly usable, but lack the depth and polish expected of production tools.

• Document output schemas for all tools. Include example JSON responses and field descriptions. At minimum, for get_webset, return {id, externalId, items_count, created_at, updated_at, ...}; for list_websets, return {websets: [{id, externalId, ...}], total_count, has_more}.
• Expand descriptions for read-only tools to 50-100 characters. E.g., change 'List all websets' to 'List all websets in your account with creation dates and item counts. Use this to discover existing collections before creating or searching.'
• Add tool annotations to all tools: readOnlyHint=true for list_*, get_*, preview_*; destructiveHint=true for delete_*; idempotentHint=true for create_* (if truly idempotent on retry with same external ID).
• Add pagination parameters to list_* tools: limit (default 20, min 1, max 100), offset (default 0). Return total_count and has_next in responses so agents know whether to paginate.
• Add error handling guidance to tool descriptions. E.g., create_webset: 'Returns 400 if externalId is not unique within your account. Returns 401 if API key is invalid. Returns 429 if rate limited, wait 60s and retry.'
• For update_webset, add explicit description of what can be updated (metadata fields only? Can you change searchQuery after creation?). Current description 'Update webset metadata' is too vague.
• For parameter descriptions, expand format/constraint explanations. E.g., searchCount 'Number of items to search for (1-1000, default 10)' instead of just '(default: 10, min: 1)'. Add enum constraints for searchBehavior, entity.type, and format fields.

Inferred effective spec: 2026-07-28+.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry