create-survey
Server Details
Create AI surveys with dynamic follow-up probing directly from your AI assistant.
- Status
- Healthy
- Uptime
- 100.0% over 37 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- feedbk-ai/feedbk-mcp-server
- GitHub Stars
- 2
- Server Listing
- AI Survey Creator MCP Server
TDQS
Scored across 1 tool
With only one tool, there is no ambiguity or overlapping purposes. The tool's purpose is clearly defined as a conversational interface to survey builder agent, making it impossible to misselect.
The single tool name 'survey_builder' is descriptive and follows a clear snake_case convention. There are no other tools to conflict with, so naming is consistent.
Having a single tool is borderline for the scope of the server. While the tool is designed as an agent that handles multiple survey operations, the tool surface feels thin compared to a typical dedicated survey management system.
The tool description claims to cover create, edit, preview, publish, close, and analyze, covering the core survey lifecycle. However, it omits explicit mention of delete, list, or other administrative operations, leaving minor gaps.
Available Tools
1 toolsurvey_builderAInspect
Send a message to the feedbk survey-builder agent. It can create, edit, preview, publish, close, and analyze AI-moderated surveys. Omit session_id on the first call; pass the session_id from the previous response on follow-up calls to continue the conversation (sessions expire after an hour of inactivity).
| Name | Required | Description | Default |
|---|---|---|---|
| message | Yes | ||
| session_id | No |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Since no annotations are provided, the description carries the full burden. It discloses the conversational nature, the agent's ability to perform mutating actions (publish, close), and session expiry. Missing response format and error behavior keeps it from a 5.
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-load purpose and include essential session-handling rules without any fluff. Every sentence serves a purpose, making it concise and well-structured.
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?
Given the tool's simplicity (2 params, no output schema), the description covers the operation and the key workflow (session management). It doesn't specify the response structure beyond implying session_id, but that is adequate for this complexity.
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?
The schema has 0% description coverage, so the description must compensate. It clarifies 'message' as the content to send and thoroughly explains 'session_id' semantics. While message format isn't elaborated, the session guidance adds substantial meaning beyond the bare schema.
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?
The description clearly states that the tool sends a message to a survey-builder agent and enumerates its capabilities (create, edit, preview, publish, close, analyze). This offers a specific verb+resource with no ambiguity, and since there are no siblings, it inherently distinguishes itself.
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 instructs when to omit session_id on the first call and when to pass it on follow-ups, providing clear when/when-not guidance. It also warns about session expiration, ensuring the agent knows the operational constraints.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
6 tool updates
- Removed
create_edit_survey - Removed
preview_survey - Removed
save_survey - Removed
share_survey - Added
survey_builder - Removed
view_responses
5 tool updates
- Added
create_edit_survey - Removed
create_survey - Added
preview_survey - Changed
save_survey25 fields changed- added
Input schema / properties / guide / properties / duration / maximumAdded value: +120 - added
Input schema / properties / guide / properties / duration / minimumAdded value: +1 - changed
Input schema / properties / guide / properties / duration / typePrevious value: -"number"New value: +"integer" - added
Input schema / properties / guide / properties / goal / maxLengthAdded value: +2000 - added
Input schema / properties / guide / properties / lang / maxLengthAdded value: +10 - added
Input schema / properties / guide / properties / name / maxLengthAdded value: +200 - changed
Input schema / properties / guide / properties / questions / items / properties / choices / anyOfPrevious value: -[ - { - "items": { - "additionalProperties": false, - "properties": { - "text": { - "type": "string" - } - }, - "required": [ - "text" - ], - "type": "object" - }, - "type": "array" - }, - { - "type": "null" - } -]New value: +[ + { + "items": { + "additionalProperties": false, + "properties": { + "text": { + "maxLength": 500, + "type": "string" + } + }, + "required": [ + "text" + ], + "type": "object" + }, + "maxItems": 50, + "type": "array" + }, + { + "type": "null" + } +] - added
Input schema / properties / guide / properties / questions / items / properties / condition / anyOfAdded value: +[ + { + "maxLength": 500, + "type": "string" + }, + { + "type": "null" + } +] - removed
Input schema / properties / guide / properties / questions / items / properties / condition / typeRemoved value: -[ - "string", - "null" -] - added
Input schema / properties / guide / properties / questions / items / properties / follow_up_goal / anyOfAdded value: +[ + { + "maxLength": 500, + "type": "string" + }, + { + "type": "null" + } +] - removed
Input schema / properties / guide / properties / questions / items / properties / follow_up_goal / typeRemoved value: -[ - "string", - "null" -] - added
Input schema / properties / guide / properties / questions / items / properties / framing / anyOfAdded value: +[ + { + "maxLength": 2000, + "type": "string" + }, + { + "type": "null" + } +] - removed
Input schema / properties / guide / properties / questions / items / properties / framing / typeRemoved value: -[ - "string", - "null" -] - added
Input schema / properties / guide / properties / questions / items / properties / id / maxLengthAdded value: +64 - added
Input schema / properties / guide / properties / questions / items / properties / rating_levels / maximumAdded value: +10 - added
Input schema / properties / guide / properties / questions / items / properties / rating_levels / minimumAdded value: +2 - changed
Input schema / properties / guide / properties / questions / items / properties / rating_levels / typePrevious value: -"number"New value: +"integer" - added
Input schema / properties / guide / properties / questions / items / properties / rating_max_label / anyOfAdded value: +[ + { + "maxLength": 100, + "type": "string" + }, + { + "type": "null" + } +] - removed
Input schema / properties / guide / properties / questions / items / properties / rating_max_label / typeRemoved value: -[ - "string", - "null" -] - added
Input schema / properties / guide / properties / questions / items / properties / rating_min_label / anyOfAdded value: +[ + { + "maxLength": 100, + "type": "string" + }, + { + "type": "null" + } +] - removed
Input schema / properties / guide / properties / questions / items / properties / rating_min_label / typeRemoved value: -[ - "string", - "null" -] - added
Input schema / properties / guide / properties / questions / items / properties / text / maxLengthAdded value: +2000 - added
Input schema / properties / guide / properties / questions / maxItemsAdded value: +100 - added
Input schema / properties / guide / properties / redirect_text / maxLengthAdded value: +500 - removed
Input schema / properties / guide / properties / redirect_urlRemoved value: -{ - "default": "/redirect.html?return=complete", - "type": [ - "string", - "null" - ] -}
- Changed
share_survey1 field changed- changed
Input schema / properties / project_token / descriptionPrevious value: -"Project token (format: projectId:secret)"New value: +"Your project token (format: projectId:secret)"
5 tool updates
- Removed
analyze_question - Removed
analyze_survey - Removed
archive_survey - Removed
save_simulated_response - Removed
simulate_responses
2 tool updates
- Changed
save_simulated_response1 field changed- changed
Input schema / properties / answers / descriptionPrevious value: -"Answers keyed by question ID (e.g. q1, q2). Skip q0."New value: +"Answers keyed by question ID (e.g. q1, q2)."
- Changed
save_survey5 fields changed- removed
Input schema / properties / guide / properties / intro_framingRemoved value: -{ - "default": "Hallo! Willkommen zur Umfrage.", - "type": "string" -} - removed
Input schema / properties / guide / properties / intro_noRemoved value: -{ - "default": "Nein", - "type": "string" -} - removed
Input schema / properties / guide / properties / intro_textRemoved value: -{ - "default": "Können wir starten?", - "type": "string" -} - removed
Input schema / properties / guide / properties / intro_yesRemoved value: -{ - "default": "Ja", - "type": "string" -} - changed
Input schema / properties / guide / properties / redirect_text / defaultPrevious value: -"Vielen Dank für Ihre Teilnahme!"New value: +""
16 tool updates
- Changed
analyze_question3 fields changed- added
Input schema / properties / project_tokenAdded value: +{ + "description": "Your project token (format: projectId:secret)", + "type": "string" +} - removed
Input schema / properties / results_tokenRemoved value: -{ - "description": "Your edit token (format: projectId:secret)", - "type": "string" -} - changed
Input schema / requiredPrevious value: -[ - "results_token", - "question_id" -]New value: +[ + "project_token", + "question_id" +]
- Removed
analyze_results - Added
analyze_survey - Added
archive_survey - Added
create_survey - Removed
edit_survey - Removed
publish_survey - Changed
save_simulated_response3 fields changed- added
Input schema / properties / project_tokenAdded value: +{ + "description": "Your project token (format: projectId:secret)", + "type": "string" +} - removed
Input schema / properties / results_tokenRemoved value: -{ - "description": "Your edit token (format: projectId:secret)", - "type": "string" -} - changed
Input schema / requiredPrevious value: -[ - "results_token", - "answers" -]New value: +[ + "project_token", + "answers" +]
- Changed
save_survey4 fields changed- added
Input schema / properties / guide / properties / goalAdded value: +{ + "default": "", + "type": "string" +} - added
Input schema / properties / project_tokenAdded value: +{ + "description": "Project token (format: projectId:secret). Omit to create a new survey.", + "type": "string" +} - removed
Input schema / properties / results_tokenRemoved value: -{ - "description": "Your edit token (format: projectId:secret)", - "type": "string" -} - changed
Input schema / requiredPrevious value: -[ - "guide", - "results_token" -]New value: +[ + "guide" +]
- Removed
set_status - Added
share_survey - Changed
simulate_responses3 fields changed- added
Input schema / properties / project_tokenAdded value: +{ + "description": "Your project token (format: projectId:secret)", + "type": "string" +} - removed
Input schema / properties / results_tokenRemoved value: -{ - "description": "Your edit token (format: projectId:secret)", - "type": "string" -} - changed
Input schema / requiredPrevious value: -[ - "results_token" -]New value: +[ + "project_token" +]
- Removed
start_survey - Added
view_responses - Removed
view_results - Removed
view_survey
8 tool updates
- Added
analyze_question - Added
analyze_results - Changed
publish_survey1 field changed- removed
Input schema / properties / results_tokenRemoved value: -{ - "description": "Optional: provide to update an existing survey instead of creating a new one", - "type": "string" -}
- Added
save_simulated_response - Added
save_survey - Added
set_status - Added
simulate_responses - Added
view_survey
1 tool update
- Added
view_results
1 tool update
- Changed
publish_survey3 fields changed- removed
Input schema / properties / guide / properties / questions / items / properties / ai_probingRemoved value: -{ - "default": true, - "type": "boolean" -} - added
Input schema / properties / guide / properties / questions / items / properties / follow_up_countAdded value: +{ + "default": 1, + "maximum": 3, + "minimum": 0, + "type": "number" +} - added
Input schema / properties / guide / properties / questions / items / properties / follow_up_goalAdded value: +{ + "type": [ + "string", + "null" + ] +}
2 tool updates
- Added
edit_survey - Changed
publish_survey1 field changed- added
Input schema / properties / results_tokenAdded value: +{ + "description": "Optional: provide to update an existing survey instead of creating a new one", + "type": "string" +}
2 tool updates
- First observed
publish_survey - First observed
start_survey
Related MCP Connectors
Create and edit surveys, read responses, and reply to users — from your AI assistant.
Create, edit and publish surveys, then read results from your AI chat.
1- AskLoopOAuthapp.askloop
Create and run surveys by chatting. Respondents just open a link — no AI, no account.
Build, target, launch and analyse consumer surveys from your AI assistant (Survey Light, 71 tools).
Related MCP Servers
- AlicenseNot gradedqualityFmaintenanceEnables LLMs to conduct dynamic, conversational surveys with skip logic, session resume, and pluggable storage.56 npm4Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to conduct user research workflows directly from Great Question, including creating studies, recruiting participants, and querying insights.MIT
- FlicenseNot gradedqualityDmaintenanceAI-powered persona analysis and Focus Group Interview (FGI) system that creates dynamic personas from survey responses, generates contextual follow-up questions, tracks data freshness scores, and provides business insights on preferences and trends.2-
- AlicenseCqualityBmaintenanceRun real user interviews from AI agents and retrieve structured insights with themes and verbatim quotes.52 npm5MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.