Content
61%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a well-structured, actionable reference for driving Mixpanel via Rube MCP, with exact tool slugs, parameters, expression syntax, and per-workflow pitfalls — genuinely useful API knowledge Claude would not know. Its weaknesses are redundant repetition of date-format and expression-syntax material across sections, and the absence of validation steps around the batch profile-update operation, which caps workflow clarity.
Suggestions
Add an explicit validation checkpoint before MIXPANEL_PROFILE_BATCH_UPDATE (e.g., run MIXPANEL_QUERY_PROFILES, confirm the matched set, then apply the batch update, and re-query to verify) to provide the missing feedback loop.
Consolidate the duplicated date-format and Mixpanel expression-syntax guidance into the "Known Pitfalls" section only, and reference it from the workflows, to remove the repeated blocks.
Include one complete worked example (tool sequence with an assembled parameter payload for a common case like a 30-day segmentation query) to close the actionability gap.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and Mixpanel-specific with no explanation of concepts Claude already knows, but material is repeated across sections — 'YYYY-MM-DD' date format appears in workflow 1 and again under "Known Pitfalls > Date Formats", and Mixpanel expression syntax is covered three times (workflow 2 pitfalls, "Common Patterns > Mixpanel Expression Syntax", and "Known Pitfalls > Expression Syntax") — so it could be meaningfully tightened. | 3 / 5 |
Actionability | Guidance is concrete and mostly executable: exact tool slugs (MIXPANEL_AGGREGATE_EVENT_COUNTS), parameter names with types and formats ('unit': 'minute'...'month'), and copy-ready expression examples like `properties["country"] == "US"`. It falls short of a 5 only in lacking any full example request or end-to-end worked invocation showing the parameters assembled together. | 4 / 5 |
Workflow Clarity | Sequences are clearly ordered with [Prerequisite]/[Required] tags and setup includes verification ("Confirm connection status shows ACTIVE before running any workflows"), but the workflow involving the batch operation MIXPANEL_PROFILE_BATCH_UPDATE has no validation/feedback loop (e.g., query-and-verify profiles before applying $set/$unset operations), which caps workflow clarity at 3 per the rubric's batch-operation rule. | 3 / 5 |
Progressive Disclosure | The single file is well organized: per-workflow sections with "When to use", a Common Patterns section, and a Quick Reference table that acts as navigation; there are no nested or buried references. It falls short of 5 because at ~220 lines the per-tool parameter and pitfall detail could plausibly live in one-level-deep reference files, and no such split exists. | 4 / 5 |
Total | 14 / 20 Passed |