This guide provides ready-to-use prompts for working with your Document360 knowledge base through an AI assistant connected via MCP. Prompts are organized by task so you can find what you need based on what you're trying to accomplish, not which tool is involved.
For details on what each tool does and its parameters, refer to the Supported MCP tools article.
Before you start
Effective MCP prompts share a few common traits:
Be specific about versions and languages when your knowledge base has multiple. Vague prompts may return results from the wrong version.
Chain tasks naturally - MCP tools work well in sequence. You can search, retrieve, and update in a single prompt.
State your intent - tell the AI assistant what you're trying to achieve, not just what to fetch. It will select the right tools automatically.
Verify before publishing - MCP write operations create drafts. Always review in Document360 before publishing.
Search your knowledge base
Use these prompts when you want to discover what content exists, find articles on a topic, or identify gaps before writing.
Find existing coverage on a topic - "Search my knowledge base for everything related to setting up SSO. Show me what's covered and flag any gaps."
Search within a specific version - "Find all articles in version 3.0 that mention the API key setup process."
Check for content before creating something new - "I'm writing a release note for our new analytics dashboard. Search Document360 for existing articles on analytics so I don't duplicate content."
Find an article to share with a customer - "A customer is asking about workspace permissions. Search my knowledge base and give me the most relevant article to share."
Audit coverage across a topic area - "Search for all articles related to billing and payments. List them with a one-line summary of each so I can spot overlaps or gaps."
Find articles that may be outdated - "Search for articles that mention the Starter plan. I want to review them — we've changed our pricing."
Retrieve articles and categories
Use these prompts when you need to read, review, or summarize existing content before acting on it.
Read and rewrite an article's introduction - "Fetch the article on 'Getting started with Document360' and rewrite the introduction to be more welcoming for non-technical users."
Review a draft for completeness - "Get the current draft of our onboarding guide and tell me if anything looks outdated or incomplete."
Check a translation for consistency - "Retrieve the French version of our billing FAQ and check whether the translation is consistent with the English version."
Summarize an article for a customer email - "Pull the article on custom domains and summarize it in three bullet points so I can include it in a customer email."
Browse the knowledge base structure - "Show me the full category structure for version 2.0. I want to understand how our documentation is organized before we do the Q3 restructure."
Identify thin categories - "Get the category list and tell me which sections have fewer than three articles — those are the gaps I want to fill first."
Inspect a specific category - "Get the details of our 'Integrations' category and list every article in it. I want to check if our Zapier and Slack docs are up to date."
Understand structure before onboarding a new writer - "Fetch our category structure and write a short briefing document explaining how our knowledge base is organized."
Find the right place for a new article - "List all top-level categories so I can decide where a new article on team management should live."
Create new articles
Use these prompts when you want to draft and create new documentation. MCP creates articles as drafts — review them in Document360 before publishing.
Search first, then create if nothing exists - "Search my knowledge base for articles on team roles. If there's nothing on custom roles, create a new article in the 'Account settings' category explaining how to set them up."
Create an article based on a customer question - "A customer keeps asking how to embed Document360 into their website. Check if we have an article on this — if not, draft and create one in the 'Getting started' category."
Document a new feature - "We just launched a dark mode feature. Create a new article in the 'Customization' category covering how to enable it, with a note that it's available from version 4.0 onwards."
Draft an article from a ticket - "Here's a support ticket describing a common setup issue: [paste ticket]. Check if we have documentation for this. If not, draft a new article in the 'Troubleshooting' category."
Generate a first draft for review - "Create a draft article in the 'API reference' category explaining how to authenticate with our API using OAuth 2.0. I'll review and refine it before publishing."
Update existing articles
Use these prompts when content needs to change — after a product update, pricing change, rebrand, or UX change.
Update steps after a UI change - "Fetch our 'Importing content' article and update the step-by-step section to reflect the new drag-and-drop interface we launched last week."
Update pricing references across articles - "Our pricing changed. Find every article that mentions the Starter plan and update the pricing references to match the new structure."
Fix a specific section without touching the rest - "The article on configuring custom domains has a broken flow in step 4. Fetch it, fix the steps, and update it. Don't change anything else."
Add a new section to an existing article - "Fetch our most-viewed article on editor shortcuts and add a new section for the keyboard shortcuts we added in the last release."
Refresh an outdated introduction - "Fetch the 'Getting started' article and update the intro paragraph. It still references our old interface. Keep everything else the same."
Create and update categories
Use these prompts when you need to reorganize your knowledge base, add new sections, or update how categories are named and structured.
Create a category for a new product tier - "We're launching an enterprise tier next month. Create a new top-level category called 'Enterprise features' in version 5.0 so I can start adding articles to it."
Break up a crowded category with subcategories - "Our 'Integrations' section is getting crowded. Create subcategories for 'CRM integrations', 'Productivity tools', and 'Developer tools' so we can organize it better."
Set up a new onboarding structure - "I'm building out a new onboarding flow for admins. Create a category called 'Admin setup guide' and add three subcategories: 'Users', 'Permissions', and 'Branding'."
Rename a category - "Rename the 'Getting started' category to 'Quick start guide'."
Reorder categories for better discoverability - "Move the 'Billing and payments' category to appear before 'Account settings' in the navigation. It's getting more traffic and should be easier to find."
Update category visibility - "The 'Legacy features' category should only be visible to internal team members. Update its visibility settings so it's hidden from the public knowledge base."
Refresh a category's intro text - "The intro text on our 'API reference' category page is two years old. Rewrite it to reflect that we now support REST and webhooks, and update the category page."
Multi-step workflows
Use these prompts for more complex tasks that chain multiple operations together — search, retrieve, create, and update in a single instruction.
Identify and fill a documentation gap - "Search my knowledge base for articles on user permissions. Retrieve the most relevant ones. If there's no article covering custom roles specifically, create one in the 'Account settings' category."
Audit and update a whole section - "Get all articles in the 'Troubleshooting' category. Identify any that haven't been updated recently or that look incomplete, and suggest what each one needs. Then update the weakest one."
Prepare a release - "We're releasing version 4.0 next week. Search for all articles that reference version 3.0 features and list which ones need updating. Then update the top three most critical ones."
Restructure and document - "Show me the category structure for version 2.0. Based on it, create a new 'Quick reference' category and draft a summary article that links to the five most important articles in the knowledge base."
Support ticket to documentation - "Here's a support ticket we keep getting: [paste ticket]. Search to see if we have documentation covering this. If we do, fetch it and improve the clarity. If we don't, create a new article in the most appropriate category."
Tips for better prompts
Specify the version when it matters - Prompts like "search my knowledge base" run across all versions by default. Add "in version 3.0" or "in the latest version" when precision matters.
Tell the AI what not to change - When updating articles, add "don't change anything else" or "keep all other sections intact" to prevent unintended edits.
Confirm before write operations - For sensitive updates, add "show me what you plan to change before making the update" to review before changes are applied.
Use article URLs for precision - If you know the exact article you want to retrieve or update, include its URL in the prompt. This is faster and more accurate than searching by title.
Chain searches with actions - Combine search and write in one prompt: "Search for X, and if nothing relevant exists, create a new article on Y." The AI assistant will search first and only create if needed.