fix(tools): rename labels tools to scenario-labels for naming consistency - #89
Merged
Andrii Chumak (andriichumak) merged 2 commits intoAug 26, 2026
Conversation
…ency
The MCP tools for scenario labels used a bare "labels" category/prefix while every
other endpoint follows the {category}_{action} convention matching its file name
(scenario-labels.ts). This risked future naming collisions with unrelated label
concepts and broke consistency across the tool catalog.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR standardizes the MCP tool naming for scenario labels by renaming the tool category and tool-name prefix from labels to scenario-labels, aligning with the repository’s {category}_{action} convention and the underlying scenario-labels endpoint.
Changes:
- Renamed scenario-label MCP tool names from
labels_*toscenario-labels_*and updated theircategory. - Updated references in scenario tool docs/tests and the README tool-category list.
- Bumped the package version to
1.6.12(and syncedpackage-lock.json).
Reviewed changes
Copilot reviewed 5 out of 6 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| test/scenario-labels-tools.spec.ts | Updates tool-name expectations in MCP tool tests. |
| src/endpoints/scenarios.tools.ts | Updates documentation string referencing the renamed discovery tool. |
| src/endpoints/scenario-labels.tools.ts | Renames tool identifiers and category to scenario-labels. |
| README.md | Updates the tool category list to reflect the new category name. |
| package.json | Bumps package version. |
| package-lock.json | Syncs lockfile version to match package.json. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| { | ||
| "name": "@makehq/sdk", | ||
| "version": "1.6.11", | ||
| "version": "1.6.12", |
Andrii Chumak (andriichumak)
approved these changes
Aug 26, 2026
Andrii Chumak (andriichumak)
deleted the
fix/BAR-3814-rename-scenario-labels-tools
branch
August 26, 2026 11:00
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
categoryand name prefix fromlabelstoscenario-labels, matching the{category}_{action}convention every other endpoint follows (and the underlyingscenario-labels.tsfile/ScenarioLabelsclass).labelsrisked future naming collisions and was inconsistent with the rest of the tool catalog.Changed tools
labels_list→scenario-labels_listlabels_create→scenario-labels_createlabels_update→scenario-labels_updatelabels_delete→scenario-labels_deletelabels_assign→scenario-labels_assignlabels_unassign→scenario-labels_unassignNo SDK method, class, or mock fixture names changed — this is scoped to the MCP tool layer (name/category) plus one doc reference in
scenarios.tools.tsand the README tool-category list. Confirmedmake-mcp-server-hosthas no dependency on the old tool names.Test plan
npm run linttest/scenario-labels-tools.spec.tspasses with updated tool names