Best practices for MCP prompting

Effective prompting is key to getting the most out of your Tricentis Test Management for Jira MCP integration. This topic provides best practices, examples, and troubleshooting for natural language interactions.

Before you start

Before you jump into prompting with the Tricentis Test Management for Jira MCP, be sure you've already taken these steps:

After these two processes are complete, you're ready to start prompting.

Core principles

Follow these fundamental principles to create effective MCP prompts:

  • Be clear and specific: Specify exactly what you want to achieve and include relevant constraints.

  • Provide context: Make sure you provide the AI with enough context and relevant information, like project keys, to complete the task.

  • Use progressive refinement: Start broad, then narrow down based on results.

  • Structure complex requests: Break complex tasks into clear, logical steps.

Example prompts

Use these prompts to take advantage of the available MCP actions for Tricentis Test Management for Jira.

If you're directly referencing a specific object, such as an epic, project, requirement, or bug, you need to give the MCP the key number for that object. If you've already referenced the object during your session, you don't need to include the key number again.

Keep in mind that these prompts are examples. You can adjust and build on them to better meet your needs.

Action

Example prompt

Required input

Create folders for epic features

Please create multiple test folders organized by key features that are covered by the epic YOUR EPIC KEY and describe the folders you created.

Epic key

Create requirements from epic

Please create key requirements based on the epic YOUR EPIC KEY.

Epic key

Create tests for requirements

Create tests for requirement YOUR REQUIREMENT KEY and put them in suitable folders. Use the existing folders that are included in the project.

Requirement key

Add test details

I created a test called "Login to google.com". Please add preconditions and steps to it.

 

Organize existing tests

Move this test (the test we discussed) to the proper folder in case it is in the wrong folder. If you need to create a new folder, create that folder.

 

Create tests for bug verification

Please create a few tests that are related to bug YOUR BUG KEY and put them in the proper folders (use existing folders if we have suitable folders. If needed, create folders).

Bug key
Get test case by project Show me all the test cases from the "MobileAppV2" project, including test steps, priority, and assigned testers. Please paginate the results if there are more than 100 entries.  
Delete test case Delete all test cases that have the label "API".  
Get test cases folders Retrieve all test case folders from the "InventoryManagementSystem" project. Include folder names and their order under parent folders. I want to organize the folder structure by creation date and hierarchy to improve navigation.  
Link a requirement to a test case Link the requirement YOUR REQUIREMENT KEY to the test case "Add single item to cart". Requirement key

Generate example tests

Create 3 example tests in project YOUR_PROJECT_KEY.

Project key

Troubleshooting

You might run into the error 401 Unauthorized or Authentication failed. Here are the steps you can take to resolve it:

  • Verify your Tricentis Test Management for Jira API key is correct and has proper permissions.

  • Make sure that you use the correct MCP server URL.

  • Clear your browser cache and retry.