Tutor LMS MCP for course building, quizzes and results

Finding the quiz question every learner gets wrong

A Tutor LMS MCP session that pays for itself quickly starts from the results rather than the content. tutor-lms-get-grades summarises one course per learner and quiz: attempts, best and latest percentage, the latest result and whether the passing grade was reached. A quiz where most learners pass only on a second or third attempt is the place to look. tutor-lms-list-quiz-attempts narrows to that quiz, and tutor-lms-get-quiz returns its questions with the correct answers marked, so the agent can point at a question whose wording or answer key looks wrong.

Attempt lists do not include learners' individual answers, so the agent cannot say which option people chose; it can say a quiz is failing more often than its neighbours and show you the questions to reread. Names and grades are still personal data even without emails, and they are sent to whichever AI provider your client uses, so keep these reads to the people who already see Tutor's reports.

Fixing a Tutor LMS question after learners have taken the quiz

tutor-lms-update-quiz-question rewrites a question's text, mark and flags, and when answers are sent it replaces all of them; the question type cannot change. Questions live in Tutor's own tables, so the change log cannot undo the edit, and the response carries the previous question and answers instead. Keep that response until you have checked the quiz in Tutor's builder.

Deleting a question is the heavier choice. The dry run of tutor-lms-delete-quiz-question returns the rows that would go and how many recorded attempt answers point at the question, which tells you how much quiz history refers to it. When that number is high, editing the wording usually serves learners better than deleting. Matching, ordering, image and Tutor Pro's interactive question types are read-only here and are edited in the quiz builder.

Quiz settings: attempts, passing grade and answer feedback

tutor-lms-update-quiz-settings changes only the settings you name and can be rolled back from the change log. passing_grade is a percentage, attempts_allowed switches the attempt limit on, time_limit takes a value with a unit from seconds to weeks, and max_questions sets how many questions are drawn per attempt from a larger pool. feedback_mode takes default, reveal or retry, and GoBuildWP maps it onto the two flags Tutor 4 uses, so the agent does not have to know the newer storage.

A new passing grade is meant for attempts made after the change; how Tutor treats results already recorded, and any certificate that depends on them, is worth checking on a staging copy with a test learner before changing a live course.

Moving lessons between topics with tutor-lms-reorder-course-content

Restructuring a curriculum is one call, and it is strict on purpose: every current topic and every lesson, quiz and assignment must appear exactly once, with its new topic and position. Run it with dry_run first to see the planned moves, then for real. The change log cannot reverse a reorder; the response's restore_topics is the way back, so keep it.

The authoring abilities accept a user who can manage options or holds Tutor's manage_tutor capability, but GoBuildWP's own check, manage options, comes first, so an instructor account cannot run them. On Production Safe, deleting content and enrolling or unenrolling wait for confirm; Read Only allows the reporting reads. The Tutor LMS reference has every parameter.

• "Read only: which quiz in the Sourdough course takes learners the most attempts to pass?"
• "Show me question 4 of that quiz with its answer key, and suggest clearer wording. Change nothing yet."
• "Move the Hydration lesson into the Starter topic, after the first lesson, and show me the dry run."