Actually Asked
Server Details
Review what visitors asked on your website, publish FAQ answers written from your own pages, and follow up on visitors who left an email.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- Actually Asked
TDQS
Scored across 34 tools
Tools target clearly distinct resources (FAQ entries, groups, page rules, questions, leads, placements, settings, content), and verbs indicate the action. Minor overlap exists between update_faq_entry (which can publish a suggestion when wording changes) and publish_faq_entries, but descriptions and names keep misselection risk low.
All tools use consistent snake_case verb_noun naming (e.g., list_faq_entries, update_page_rule, preview_faq_for_page) with no mixed conventions or vague names. The pattern is predictable across all 34 tools.
34 tools is well beyond the 3-15 sweet spot and exceeds the 25-tool threshold for 'too many.' While the domain is broad, many granular operations (e.g., reorder_faq_groups, reorder_pinned_entries, restore_faq_entry) could potentially be consolidated, making the set feel heavy for an agent to navigate.
Coverage is strong: full CRUD for FAQ entries, groups, and page rules; question and lead lifecycle; widget settings; install checks; content search; and preview. Minor gaps exist (no get_faq_group, get_page_rule, or get_lead single-item retrieval), but list tools mostly compensate.
Publisher details
- Operator
- Actually Asked · Publisher source
- Operator website
- Not applicable
- Vendor relationship
- Not applicable
- Documentation
- https://actuallyasked.com/mcp · Publisher source
- Privacy policy
- Not provided
- Trust center
- Not applicable
- Restrictions
- Not applicable
Available Tools
34 toolscheck_installCheck the installARead-onlyIdempotentInspect
Checks that the widget is on a site. For a web site, reads one page (its URL must be on the site's domain or allowed domains) and reports whether the script and a container with this site's key are in its HTML, with any tag and layout. A page built in the browser may only show the widget once a visitor loads it: last_seen_at is when a visitor's browser last reached the widget. For a Shopify store, reads the live theme for the app embed and the FAQ block.
Inputs: url, site_id. Returns: installed, last_seen_at
create_faq_entryAdd a FAQ entryAInspect
Adds a question and answer to a site's FAQ, published at once, as the merchant's own (the system never rewrites it). Optionally in a group (Starter and up), with a page rule or tag of its own (Growth and up), and pinned to the top of its group. Check first that the FAQ doesn't already have the question (list_faq_entries with query).
Inputs: answer (required), question (required), tag, pinned, +3 more. Returns: entry
create_faq_groupAdd a FAQ groupAInspect
Adds a group (a heading questions sit under, like Shipping or Returns) at the end of the site's groups. It shows on every page (the Everywhere rule) unless given a page rule or tag (Growth and up). Starter and up. Actually Asked then suggests which live entries belong in it (list_placement_suggestions); move entries yourself with update_faq_entry.
Inputs: name (required), tag, site_id, page_rule_id. Returns: group
create_page_ruleAdd a page ruleBInspect
Adds a page rule: a part of the site picked out by paths, each an exact path (/pages/care) or a prefix ending in * (/products/*). Groups and entries given this rule show on the pages it matches. Growth and up. Actually Asked then suggests which entries belong there (list_placement_suggestions).
Inputs: name (required), paths (required), site_id. Returns: page_rule
delete_faq_groupDelete a FAQ groupADestructiveInspect
Deletes a group for good. Its questions stay in the FAQ, in no group. General can't be deleted. Ask the merchant before deleting.
Inputs: group_id (required), site_id. Returns: deleted
delete_page_ruleDelete a page ruleADestructiveInspect
Deletes a page rule for good. Groups on it go back to Everywhere; entries with it as their own rule lose it. Everywhere, Home and FAQ page can't be deleted. Ask the merchant before deleting.
Inputs: page_rule_id (required), site_id. Returns: deleted
discard_questionDiscard a questionADestructiveInspect
Deletes a visitor question for good. Only an unanswered question with no email (noise, spam) can be discarded; a lead or an answered question is kept. Ask the merchant before discarding.
Inputs: question_id (required), site_id. Returns: discarded
draft_faq_suggestionsDraft suggestionsAInspect
Asks Actually Asked to draft more FAQ entries from the site's pages now, rather than at the next read. Only when no suggestions are waiting: review those first. The drafts appear as suggested entries in a few minutes (list_faq_entries with state suggested). A few drafts an hour at most per site.
Inputs: site_id. Returns: drafting
get_documentRead a pageARead-onlyIdempotentInspect
The text of one page, product, policy or file part Actually Asked has read, by the document_id search_site_content gave. Long pages are cut at 20,000 characters. A file is cited as a file: never link to it.
Inputs: document_id (required), site_id. Returns: document
get_faq_entryGet a FAQ entryARead-onlyIdempotentInspect
One FAQ entry in full: the answer as markdown, its group, its own page rule and tag, its pin, where it came from, whether the merchant edited it (the system never rewrites those), and whether it may be out of date. A suggestion also says where publishing it puts it, and any entry lists the groups and page rules suggested for it.
Inputs: entry_id (required), site_id. Returns: entry
get_install_instructionsGet install instructionsARead-onlyIdempotentInspect
How to put the FAQ widget on a site: the snippet with this site's key, the full FAQ page and tag variants, and where they go on the site's platform. check_install confirms it's on a page.
Inputs: platform (required), site_id. Returns: guide, platform, site_key, snippets
get_questionGet a visitor questionARead-onlyIdempotentInspect
One visitor question in full: the page it was asked on, any text the visitor highlighted (and the paragraph and heading around it), the answer they were given and the pages it came from, the FAQ entry it matched, the visitor's email if they left one, and whether it can be discarded.
Inputs: question_id (required), site_id. Returns: question
get_widget_settingsGet the widget's settingsARead-onlyIdempotentInspect
What the FAQ widget says and how it looks on a site: how many questions it shows, its heading, hint and ask item, and its look (preset, layout, colours and sizes; null is the site's own). A Shopify store's look is set in its theme editor, so it has none here. update_widget_settings changes them.
Inputs: site_id. Returns: widget
list_faq_entriesList FAQ entriesARead-onlyIdempotentInspect
A site's FAQ entries with a short excerpt of each answer. live (the default): published, in the order a page shows them (the entries in no group first, then each group in order; within each, pins first, then by how often visitors ask). suggested: drafted from the site's pages, waiting to be published or dismissed. removed: taken out of the FAQ; they are never suggested or published again unless restored. get_faq_entry has the whole answer.
Inputs: tag, page, query, state, +4 more. Returns: page, total, entries, next_page, +2 more
list_faq_groupsList FAQ groupsARead-onlyIdempotentInspect
A site's FAQ groups in the order a page shows them: the headings questions sit under. A group shows on the pages its page rule matches and on any page whose snippet carries its tag. Every site has General, on the FAQ page rule; it can't be renamed or deleted. Each group lists how many live entries it has and how many placements are suggested for it.
Inputs: site_id. Returns: groups, groups_applied, ungrouped_live_entries, page_rules_and_tags_applied
list_leadsList leadsARead-onlyIdempotentInspect
Visitors who left their email under a question the site couldn't answer, newest first: waiting for the merchant's reply (the default), replied, or all. The merchant replies from their own email; nothing here sends mail.
Inputs: page, filter, site_id, per_page. Returns: page, leads, total, next_page
list_page_rulesList page rulesARead-onlyIdempotentInspect
A site's page rules: parts of the site picked out by their paths (an exact path like /pages/care, or a prefix ending in * like /products/). Groups show where their rule matches, and an entry can have a rule of its own too. A page matches every rule whose path fits it. Every site has Everywhere (/), Home (/) and FAQ page (/faq); they can't be renamed or deleted, and only the FAQ page's paths can change.
Inputs: site_id. Returns: page_rules, page_rules_and_tags_applied
list_placement_suggestionsList suggested placementsARead-onlyIdempotentInspect
Where Actually Asked suggests live FAQ entries belong: a group to sit under, or a page rule to show on. Nothing moves until the merchant accepts; a declined suggestion is never made again. Optionally only those for one group or page rule.
Inputs: page, site_id, per_page, target_id. Returns: page, total, next_page, placement_suggestions
list_questionsList visitor questionsARead-onlyIdempotentInspect
What visitors asked on a site, newest first: answered (from the site's pages), matched (with an existing FAQ entry), unanswered (nothing on the site answered it: a gap worth adding to the FAQ), out_of_scope (needed live data such as an order's status). Archived questions are left out unless archived is true. get_question has the full detail.
Inputs: page, query, status, site_id, +3 more. Returns: page, total, next_page, questions
list_sitesList sitesARead-onlyIdempotentInspect
The sites in the connected account: each one's plan and what it allows (groups from Starter; page rules and tags from Growth; how many entries can be pinned), whether it's paused, whether the widget is live on it, and what's waiting: questions this month, leads waiting for a reply, suggested FAQ entries and suggested placements. Start here.
Inputs: no named parameters. Returns: sites, account
preview_faq_for_pagePreview the FAQ on a pageARead-onlyIdempotentInspect
What the FAQ shows on one page of the site, worked out exactly as the widget does: the sections (the entries in no group first, then each group in order) and their questions. widget (the default) is the top entries a normal snippet shows; full is a full FAQ page (data-faq-layout="full"). Use it to check a page rule or tag change.
Inputs: path (required), tag, layout, site_id. Returns: path, layout, sections
publish_faq_entriesPublish suggestionsAInspect
Publishes suggested entries as they are, each under its proposed group (made, with a page rule for its page, when the site doesn't have it yet). Give entry_ids, or all: true for every waiting suggestion. Read each one first (get_faq_entry) and check its answer against the site's pages; edit with update_faq_entry where it's wrong.
Inputs: all, site_id, entry_ids. Returns: published
remove_faq_entryRemove a FAQ entryAIdempotentInspect
Takes a live entry out of the FAQ, or dismisses a suggestion. It is kept, so the same question is never suggested or published again, and restore_faq_entry brings it back.
Inputs: entry_id (required), site_id. Returns: entry
reorder_faq_groupsReorder FAQ groupsAIdempotentInspect
Puts a site's groups in a new order: the order their headings show in, after the questions in no group. Give every group.
Inputs: group_ids (required), site_id. Returns: groups
reorder_pinned_entriesReorder pinned entriesAIdempotentInspect
Puts a group's pinned entries in a new order (pins show first, in this order, before the entries ranked by how often visitors ask). Give every pinned entry of the group. Pin or unpin with update_faq_entry.
Inputs: group_id (required), entry_ids (required), site_id. Returns: pinned
resolve_placement_suggestionsAccept or decline placementsADestructiveInspect
Accepts or declines suggested placements (from list_placement_suggestions). Accepting moves the entry under the group, or gives it the page rule, and settles its other suggestions of that kind; a declined one is never made again. Give suggestion_ids, or target_id to accept every suggestion for one group or page rule.
Inputs: decision (required), site_id, target_id, suggestion_ids. Returns: count, decision
restore_faq_entryRestore a FAQ entryAIdempotentInspect
Brings a removed entry back: into the FAQ if it was live, or back to the suggestions if it was a dismissed suggestion.
Inputs: entry_id (required), site_id. Returns: entry
search_site_contentSearch the site's pagesARead-onlyIdempotentInspect
Full-text search over everything Actually Asked has read for a site (its pages, products, policies and uploaded files), the same search that answers visitors. Returns the best passages with their page. Write and check FAQ answers from these, not from general knowledge. A file's passages are cited as a file: never link to them.
Inputs: query (required), site_id, source_type. Returns: passages
update_faq_entryEdit a FAQ entryADestructiveIdempotentInspect
Changes any of a FAQ entry's question, answer, group, own page rule, own tag and pin; what you leave out stays. Changing the wording makes the entry the merchant's (the system never rewrites it), clears "may be outdated", and publishes a suggestion (under its proposed group unless you give another). Moving or pinning alone changes only that. To publish a suggestion as it is, use publish_faq_entries.
Inputs: entry_id (required), tag, answer, pinned, +4 more. Returns: entry
update_faq_groupEdit a FAQ groupADestructiveIdempotentInspect
Renames a group, or changes where it shows: its page rule and its tag (Growth and up). General can't be renamed. Check the result on a page with preview_faq_for_page.
Inputs: group_id (required), tag, name, site_id, +1 more. Returns: group
update_leadMark a lead repliedAIdempotentInspect
Marks a lead replied, once the merchant has answered the visitor from their own email, or back to waiting. Nothing here sends mail.
Inputs: lead_id (required), replied (required), site_id. Returns: lead
update_page_ruleEdit a page ruleADestructiveIdempotentInspect
Renames a page rule or replaces its paths. Everywhere, Home and FAQ page can't be renamed, and only the FAQ page's paths can change.
Inputs: page_rule_id (required), name, paths, site_id. Returns: page_rule
update_questionArchive a questionAIdempotentInspect
Archives a visitor question the merchant has dealt with (it leaves the log for its Archived tab and still counts in the numbers), or brings it back.
Inputs: archived (required), question_id (required), site_id. Returns: question
update_widget_settingsChange the widgetADestructiveIdempotentInspect
Changes what the FAQ widget says and how it looks on a site: how many questions it shows, its heading, hint and ask item, and, except on Shopify, its look: a ready-made preset, the layout, colours and sizes. Give only what changes; null puts a field back to its default. Fonts always come from the site. Live within a minute; share the url so the merchant can see it in the Widget page's preview.
Inputs: ask, hint, title, layout, +7 more. Returns: widget
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Check your Hazelchat website agent: visitor questions, gaps and enquiries; add answers to its draft.
Live chat and AI agent for websites: answer visitors, manage sites, the AI agent and stats.
Create customer-service agents, review conversations and leads, and improve answers.
Read your SuperBot support conversations, find unanswered questions, and teach your AI new answers.
Related MCP Servers
- FlicenseAqualityBmaintenanceReads a small-business website like a customer would and shows where they get stuck. Every AI answer has to quote the page, and the server checks the quote before it counts.11-
- FlicenseAqualityBmaintenanceLets an AI agent ask real humans a question when the web genuinely has no answer, and get verbatim replies back with a respondent count. Built for the moment an agent is about to say "you should validate this with real users". Remote MCP, plain POST, or a single GET. No signup, no API key.2-
- AlicenseAqualityDmaintenanceEnables SEO page generation with competitor research and Schema.org structured data. Provides tools to search competitors for a keyword and generate high-quality SEO content with FAQPage schema.26 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables users to ask natural-language questions about competitors’ affiliate programs, Amazon tags, promoted products, publishing pace, and new or changed content, including optional keyword-ranking data.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.