fix: Rename duplicate 'schedule_post' tool to 'schedule_post_advanced'#3
Open
tuxxon wants to merge 1 commit into
Open
fix: Rename duplicate 'schedule_post' tool to 'schedule_post_advanced'#3tuxxon wants to merge 1 commit into
tuxxon wants to merge 1 commit into
Conversation
The server registered two tools with the same name 'schedule_post', which violates MCP protocol's unique tool name requirement and causes Claude API error: "tools: Tool names must be unique." Renamed the advanced version (with automation_settings, auto_optimize_time, auto_hashtags, etc.) to 'schedule_post_advanced' to resolve the conflict. Fixes baguskto#2 Co-Authored-By: Claude <noreply@anthropic.com>
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
2 participants
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
schedule_posttool name that violates MCP protocol's unique tool name requirementautomation_settings,auto_optimize_time,auto_hashtags) toschedule_post_advancedschedule_posttool remains unchangedProblem
The server registers two tools with the same name
schedule_post:schedule_post(basic) — simple scheduling withscheduled_publish_timeschedule_post(advanced) — automation features likeauto_optimize_time,recurring,auto_hashtagsThis causes MCP clients (e.g., Claude Code) to fail with:
Changes
src/index.ts: Renamed the secondschedule_posttool definition toschedule_post_advancedsrc/index.ts: Updated the correspondingcase 'schedule_post'handler tocase 'schedule_post_advanced'Test plan
npm run build)schedule_postand oneschedule_post_advancedin built outputFixes #2
🤖 Generated with Claude Code