[BUG] Outdated knowledge of Instagram/Meta API OAuth flow

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Claude's training data has outdated information about the Instagram/Meta API
authentication flow. Specifically:

1. Wrong OAuth endpoint: Claude suggests using https://www.facebook.com/dialog/oauth

for Instagram Business Login, but the correct endpoint is
https://www.instagram.com/oauth/authorize

1. Wrong permission scope names: Claude suggests legacy scopes like instagram_basic,

instagram_content_publish, instagram_manage_insights, pages_show_list,
pages_read_engagement. The current scopes are instagram_business_basic,
instagram_business_content_publish, instagram_business_manage_messages,
instagram_manage_comments

1. Wrong token exchange endpoints: Claude suggests using graph.facebook.com for token

exchange, but Instagram Business Login uses api.instagram.com/oauth/access_token
(short-lived) and graph.instagram.com/access_token (long-lived with ig_exchange_token
grant type)

1. Unnecessary Facebook Pages lookup: Claude assumes you need to go through Facebook

Pages to find the linked Instagram Business Account. With Instagram Business Login, you
get direct access to the IG user profile without the Pages intermediary.

The old Facebook Login flow for Instagram was deprecated. The new Instagram Business
Login flow has different endpoints, scopes, and token exchange mechanisms.

Reference: https://developers.facebook.com/docs/instagram-platform/instagram-api-with-i
nstagram-login/business-login

What Should Happen?

Improve documentation

Error Messages/Logs

Steps to Reproduce

see body

Claude Model

None

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.80 (using opus 4.6)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_