fix(zoom): request meeting_recording scope for delete-all recordings

[AYANscyy2]

Summary

Fixes #8506

The Zoom Delete Recording tool calls two different Zoom endpoints depending on whether recordingId is set, and each requires a different scope:

Endpoint	Granular scope
DELETE /meetings/{id}/recordings/{recordingId}	cloud_recording:delete:recording_file
DELETE /meetings/{id}/recordings	cloud_recording:delete:meeting_recording

Sim only declared and requested the first scope, so the delete-all path (no recording ID) used a token that Zoom rejects for a missing scope.

Changes

• tools/zoom/delete_recording.ts: require both scopes
• lib/oauth/oauth.ts, lib/oauth/utils.ts: request the new scope at consent and add its description
• Docs: add it to the Zoom scope table and the service-account scope list (:admin variant)
• Regenerate tools/generated/tool-metadata.ts via bun run tool-metadata:generate

Notes

• Existing Zoom connections must reconnect to grant the new scope before delete-all works.
• Root cause is derived from Zoom's API scope reference. The issue has no error text, and I have not run this against a live Zoom account.

Type of Change

• Bug fix

Testing

• biome check clean on changed files
• vitest run lib/oauth tools/zoom: 20 files, 294 tests pass
• tool-metadata:generate diff limited to the one Zoom entry

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my changes
• My changes generate no new warnings
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

@AYANscyy2 is attempting to deploy a commit to the Sim Team on Vercel.

A member of the Team first needs to authorize it.

[greptile-apps]

Confidence Score: 4/5

[Medium risk] Adds a new OAuth scope to the Zoom integration.

The PR is not ready to merge because existing managed Zoom connections can lose the ability to delete an individual recording file.

Findings

1.  Single-file deletion requires extra scope ▶

Summary

The PR adds Zoom’s meeting-recording deletion scope to OAuth consent, the delete-recording tool, generated metadata, and setup documentation.

• The delete-all path gains the scope it needs.
• The shared tool scope requirement also blocks some existing single-file deletion connections.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  A[Delete Recording tool] --> B{recordingId supplied?}
  B -->|Yes| C[Delete individual file]
  B -->|No| D[Delete all meeting recordings]
  C --> E[recording_file scope]
  D --> F[meeting_recording scope]
  G[Current tool-level scope check] --> H[Requires both before either path]

Loading

_{Reviews (1) · Last reviewed commit: "fix(zoom): request meeting_recording sco..."}