fix: Accept both UUID and Zoom meeting IDs in meeting tools#780
Merged
Conversation
- Show meeting ID in list_upcoming_meetings output so Claude can see it - Update get_meeting_details to try UUID first, then Zoom meeting ID - Update rsvp_to_meeting to try UUID first, then Zoom meeting ID - Update cancel_meeting to try UUID first, then Zoom meeting ID - Update add_meeting_attendee to try UUID first, then Zoom meeting ID This fixes the issue where Claude would try to use Zoom meeting IDs from meeting links but the tools only accepted our internal UUIDs. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Applied the same timezone fix to Google Calendar events that was applied to Zoom meetings in PR #779. The Z suffix was causing Google Calendar to interpret times as UTC, resulting in meetings showing 5 hours earlier than intended for ET. Renamed formatDateForZoom to formatDateWithoutZ since it's now used for both Zoom and Google Calendar. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
bokelley
added a commit
that referenced
this pull request
Jan 16, 2026
* fix: Accept both UUID and Zoom meeting IDs in meeting tools - Show meeting ID in list_upcoming_meetings output so Claude can see it - Update get_meeting_details to try UUID first, then Zoom meeting ID - Update rsvp_to_meeting to try UUID first, then Zoom meeting ID - Update cancel_meeting to try UUID first, then Zoom meeting ID - Update add_meeting_attendee to try UUID first, then Zoom meeting ID This fixes the issue where Claude would try to use Zoom meeting IDs from meeting links but the tools only accepted our internal UUIDs. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix: Strip Z suffix from Google Calendar dateTime to fix timezone Applied the same timezone fix to Google Calendar events that was applied to Zoom meetings in PR #779. The Z suffix was causing Google Calendar to interpret times as UTC, resulting in meetings showing 5 hours earlier than intended for ET. Renamed formatDateForZoom to formatDateWithoutZ since it's now used for both Zoom and Google Calendar. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
bokelley
added a commit
that referenced
this pull request
Jan 20, 2026
* fix: Accept both UUID and Zoom meeting IDs in meeting tools - Show meeting ID in list_upcoming_meetings output so Claude can see it - Update get_meeting_details to try UUID first, then Zoom meeting ID - Update rsvp_to_meeting to try UUID first, then Zoom meeting ID - Update cancel_meeting to try UUID first, then Zoom meeting ID - Update add_meeting_attendee to try UUID first, then Zoom meeting ID This fixes the issue where Claude would try to use Zoom meeting IDs from meeting links but the tools only accepted our internal UUIDs. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * fix: Strip Z suffix from Google Calendar dateTime to fix timezone Applied the same timezone fix to Google Calendar events that was applied to Zoom meetings in PR #779. The Z suffix was causing Google Calendar to interpret times as UTC, resulting in meetings showing 5 hours earlier than intended for ET. Renamed formatDateForZoom to formatDateWithoutZ since it's now used for both Zoom and Google Calendar. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
bokelley
added a commit
that referenced
this pull request
Apr 22, 2026
…t#789 The upstream fix landed (PR #789, closing #780) — issue #797 was a duplicate and is now closed. Update the storyboard YAML, schema doc, and changeset to reference the merged PR so the removal trigger is "@adcp/client release that ships #789" instead of an open issue. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
bokelley
added a commit
that referenced
this pull request
Apr 22, 2026
closes #2848) (#2885) * fix(storyboards): inject format_ids[0] via context_inputs in list_formats_integrity (closes #2848) The @adcp/client (≤5.11) list_creative_formats request builder returns {} and the runner only forwards envelope fields from sample_request. The storyboard's `format_ids: ["$context.product_format_id"]` therefore never reached the wire and the seller answered with its full unfiltered catalog, making the round-trip assertion fail by coincidence rather than because the seller substituted formats. Use the runner's context_inputs (applied after the builder) to inject the captured {agent_url, id} object at format_ids[0]; document context_inputs in the storyboard schema as a temporary bridge tied to adcontextprotocol/adcp-client#797. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(storyboards): point context_inputs comments at merged adcp-client#789 The upstream fix landed (PR #789, closing #780) — issue #797 was a duplicate and is now closed. Update the storyboard YAML, schema doc, and changeset to reference the merged PR so the removal trigger is "@adcp/client release that ships #789" instead of an open issue. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(storyboards): tighten context_inputs framing per expert review Address docs-expert feedback on #2885: - Lead the context_inputs field doc with the prohibition ("do NOT use unless …") instead of the preference, and name the observable symptom (unfiltered agent response) an author can diagnose from. - Add an inline YAML snippet in the schema doc so authors don't have to navigate to the media-buy worked example to see the shape. - Call out that context_inputs silently no-ops on a missing key (distinct from $context.<name>'s loud unresolved_substitution), so the default path has better failure modes. - Acknowledge dependency-aware multi-instance dispatch as a legitimate non-workaround use so the framing isn't "escape hatch only." - State type-preservation behavior explicitly. - Cross-reference from the sample_request field definition and the substitution-syntax section so authors land on context_inputs instead of scrolling past the field definitions. - Pin the inline comment to the currently-published @adcp/client 5.10.0 (not 5.11, which is unreleased) so the version claim doesn't drift when 5.11 ships. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <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
1 participant
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
list_upcoming_meetingsoutput so Claude can see and use themget_meeting_details,cancel_meeting,rsvp_to_meeting, andadd_meeting_attendeeto accept both UUID and Zoom meeting ID formatsProblem
Claude was getting Zoom meeting IDs from meeting links but the meeting tools only accepted internal UUIDs. This caused "Meeting not found" errors when trying to cancel or modify meetings.
Test plan
🤖 Generated with Claude Code