feat: clarifying the descriptions of user_id and DESTINATION_USER_ID … #47
+11
−10
Conversation
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
…in the README files.
|
|
eucyt
reviewed
May 1, 2025
Co-authored-by: Yuta Euchi <63095160+eucyt@users.noreply.github.com>
Co-authored-by: Yuta Euchi <63095160+eucyt@users.noreply.github.com>
Maimikuru
commented
May 1, 2025
| @@ -35,8 +35,8 @@ LINE公式アカウントとAI Agentを接続するために、LINE Messaging AP | |||
| - `message.contents.type` (enum): コンテナのタイプ。'bubble'は単一コンテナ、'carousel'は複数のスワイプ可能なバブルを示す。 | |||
| 5. **get_profile** | |||
| - LINEユーザーの詳細なプロフィール情報を取得する。表示名、プロフィール画像URL、ステータスメッセージ、言語を取得できる。 | |||
| - **Inputs:** | |||
| - `user_id` (string?): プロフィールを取得したいユーザーのユーザーID。デフォルトはDESTINATION_USER_ID。 | |||
| - **入力:** | |||
There was a problem hiding this comment.
@eucyt
I also found other places that were not in Japanese, so I have corrected them.
| @@ -56,7 +56,7 @@ Claude DesktopやClaudeなどのAI Agentに次の設定を追加してくださ | |||
| 環境変数や引数は次のように設定してください: | |||
|
|
|||
| - `CHANNEL_ACCESS_TOKEN`: (必須) チャネルアクセストークン。これを取得するには、[こちらの手順](https://developers.line.biz/ja/docs/basics/channel-access-token/#long-lived-channel-access-token)に従ってください。 | |||
| - `DESTINATION_USER_ID`: (オプション) デフォルトのメッセージ受信者のユーザーID。これを確認するには、[こちらの手順](https://developers.line.biz/ja/docs/messaging-api/getting-user-ids/#get-own-user-id)に従ってください。 | |||
| - `DESTINATION_USER_ID`: (オプション) デフォルトのメッセージ受信者のユーザーID。Toolの入力に`user_id`が含まれていない場合、`DESTINATION_USER_ID`は必ず設定する必要があります。これを確認するには、[こちらの手順](https://developers.line.biz/ja/docs/messaging-api/getting-user-ids/#get-own-user-id)に従ってください。 | |||
There was a problem hiding this comment.
@eucyt
I have changed the wording.
This is because an error occurs when the tool's input does not include user_id and DESTINATION_USER_ID is not set.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Resolve this issue
This pull request updates the documentation in both Japanese (
README.ja.md) and English (README.md) to clarify the requirements for settinguser_idandDESTINATION_USER_IDin various contexts. The changes ensure that users understand that at least one of these values must be specified.Documentation Updates:
Clarifications on
user_idandDESTINATION_USER_IDRequirements:push_text_message,push_flex_message, andget_profilesections to specify that eitheruser_idorDESTINATION_USER_IDmust be set. (README.ja.md: [1] [2];README.md: [3]DESTINATION_USER_IDenvironment variable to clarify that it is optional but either it oruser_idmust be set. (README.ja.md: [1];README.md: [2]