Nunify

Update Question

update_question

Idempotent

Update an existing question's text, type, or options in the provided event. Provide either a survey_id or assessment_id plus the question_id.

Input Schema

Name	Required	Description
`options`	No	Answer options. Required for single_select, multi_select, image_text, and ranking (min 2). Not used for file_upload.
`event_id`	Yes	Event UUID returned by search_events.
`position`	No	Position of the question. Defaults to end of list.
`survey_id`	No	Survey UUID. Provide this or assessment_id to identify the question bank.
`slider_max`	No	Maximum value for slider questions.
`slider_min`	No	Minimum value for slider questions.
`question_id`	Yes	Existing question UUID.
`is_mandatory`	No	Whether the question is mandatory. Defaults to false.
`rating_scale`	No	Rating scale (1-10). Required for rating questions.
`rating_shape`	No	Rating shape: 0=Stars, 1=Thumbs, 2=Hearts, 3=Smiley. Required for rating questions.
`assessment_id`	No	Assessment UUID. Provide this or survey_id to identify the question bank.
`question_text`	Yes	The question text. Required. If the user has not provided it, ask the user before proceeding. Never invent question text or use placeholder content.
`question_type`	Yes	Type of question: single_select, multi_select, free_text, file_upload, image_text, rating, slider, ranking. Required. If the user has not provided it, ask the user before proceeding. Never assume a question type.
`max_selections`	No	Maximum selections for multi_select questions.
`min_selections`	No	Minimum selections for multi_select questions.
`slider_step_up`	No	Step increment for slider questions.

Output Schema

Name	Required	Description	Default
`hint`	Yes
`message`	Yes
`question`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive update. The description adds that it targets an existing question in a provided event, but it does not disclose what happens to existing options or responses when question_type or options change, which would be valuable for a mutation tool.

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 tight sentences with no filler. The core update action is front-loaded, followed by the key identification constraint.

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?

Given the rich schema coverage, annotations, and an output schema, the description covers the essential action and identification requirement. It could do more to flag type-dependent parameters, but the structured schema carries that detail adequately.

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 description coverage is 100%, so all 16 parameters are already documented in the input schema. The description only names text, type, options, and the survey/assessment ID choice, adding little meaning beyond the schema itself.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific verb and resource: update an existing question's text, type, or options in a given event. It distinguishes updating from creating or deleting by saying 'existing question,' but does not explicitly name sibling alternatives such as create_question or delete_question.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a useful identification prerequisite: provide either survey_id or assessment_id plus question_id. However, it does not explain when to choose this over create_question or delete_question, nor does it cover type-specific usage conditions beyond what the schema already says.

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

All Nunify tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?