Hi YAKUB AJIBADE,
Thanks for reaching out,
Client credential flow works with application-level permission, when you are acquiring token using Client id and client secret, the me endpoint doesn't make any sense.
When you use delegated permission and acquire token after user is signed in, in that case token is issued on behalf of a user and me refers to the signed in user.
With application-level permission, your app act as daemon app which can schedule a meeting on behalf of any user. Since the token is acquired using client secret in your case, your app will not be able to identify the user. so, you should specifically pass the user id as mentioned below.
However, creating online meeting does not support application-level permissions. To use application permission for this API, tenant administrators must create an application access policy and grant it to a user to authorize the app configured in the policy to create online meetings on behalf of that user (with user ID specified in the request path).
Refer to this link with more details
for an example if you want to use client secret credentials and run graph query for a specific user you can refer to this example to read a user's email in python.
from msgraph import GraphServiceClient
graph_client = GraphServiceClient(credentials, scopes)
result = await graph_client.users.by_user_id('user-id').messages.get()
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".