Hosted Microsoft Clarity MCP server, with each action switched on or off per account.
Scored across 4 tools
execute_action and query_data are hard to distinguish: both are labeled 'Step 3 (FINAL)', require identical query_contexts prerequisites, and use nearly identical wording. prompts_menu and query_contexts are more distinct, but the core boundary between executing an action and querying data is unclear.
All names use snake_case consistently, which is good. However, prompts_menu breaks the verb_noun pattern followed by execute_action, query_contexts, and query_data, making it a minor deviation.
Four tools is a reasonable, focused set for an analytics integration, and each tool has a role in the workflow. The count is slightly thin but not problematic.
The surface covers querying data, executing actions, prompt browsing, and context discovery, but relies heavily on meta-parameters rather than explicit tools. There are notable gaps around direct account/action discovery and management operations.
Execute Microsoft Clarity action (Step 3 (FINAL) of workflow).
REQUIRED: Complete these steps first using query_contexts:
request='accounts' - Get workspace_id, brand_id AND available_actions
request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions
IMPORTANT: Always call step 2 to see the exact body structure before executing.
Rely on info from steps 1-2 to construct the action body. Follow the schema exactly.
Inputs: body (required). Returns: object
Helper for planning InsightfulPipe Microsoft Clarity data queries.
Step 1: request='accounts' – Retrieve workspace_id, brand_id, other source metadata, AND available_actions (all tables you can query).
Step 2: request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] – REQUIRED before querying. Replace with actions from available_actions to get the exact request body, required identifiers, fields, time ranges, and notes for each action.
Optional: request='available_actions' – Standalone call to list all available tables/actions (already included in accounts response).
Optional: request='brands' with brand_id + workspace_id to pull brand guidelines.
Inputs: request (required), actions, brand_id, platform, +1 more. Returns: object
Query Microsoft Clarity data (Step 3 (FINAL) of workflow).
REQUIRED: Complete these steps first using query_contexts:
request='accounts' - Get workspace_id, brand_id AND available_actions
request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions
IMPORTANT: Always call step 2 to see the exact body structure before querying.
Rely on info from steps 1-2 to construct the query body. Follow the schema exactly.
Inputs: body (required). Returns: object
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Hosted Microsoft Ads MCP server, with each action switched on or off per account.
Hosted Google Tag Manager MCP server, with each action switched on or off per account.
Hosted Google Analytics 4 MCP server, with each action switched on or off per account.
Hosted PageSpeed Insights MCP server, with each action switched on or off per account.
Add one secure layer between your agents and this server.
